Properly Revamping my DNS Service

5 pts.
Tags:
DHCP
DNS
Microsoft Windows
Networking services
New Discussion Post
ASKED: February 19, 2007  2:14 AM
UPDATED: February 19, 2007  8:08 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Discuss This Question: 3  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Swiftd
    John, You can either setup server Rex to be a primary or secondary DNS server. The different of setting it up as a primary or secondary is how it gets updated. If you make it a primary, you have to manually update the DNS records when you make changes to HappyNT's DNS records (thus having two primary DNS servers). This requires more work, but is desirable if the primary DNS dies a miserable death and needs to be recovered and because it doesn't require zone transfers between the primary and secondary servers. The primary/secondary relationship requires you to setup a Secondary zone on Rex and point the primary to HappyNT. It requires TCP port 53 allowed between the two servers to handle the zone transfers (versus just UDP 53 for DNS lookups). If you choose this method, you run the risk of someone owning the primary server and therefore being able to affect the secondary DNS as well (because of zone transfers). You can solve this by configuring Secure Dynamic Update. As far as pointing to different servers for the hosted web sites, it should be as simple as pointing the site to the proper IP address. It doesn't matter if you use the "primary DNS" on HappyNT or Rex, just where that address points to and where GoDaddy points to that servers name servers for lookup. Oh, and housekeeping.com doesn't go anywhere, but http://216.255.200.122/ goes to an "under construction" default IIS page. Under each of your DNS zones, you'll want to put an alias (CNAME) for www pointing to either the server's name or another A record for that zone where the DNS server resides. Don
    0 pointsBadges:
    report
  • JHappy
    Don, Thanks for trying to help. I've set up the johnhappy.com DNS zone as best I can, and tweeked it in every way that makes sense to me, but still can't successfully serve a www.johnhappy.com web page from RUSTY. See the result at: http://www.johnhappy.com/boat.htm I've triple checked my IIS config and my firewall on RUSTY and can not find a problem. Please use the tools at DNSStuff.com to see if you see any obvious DNS setup errors.
    0 pointsBadges:
    report
  • Swiftd
    Here's how I'm testing it: Open a command prompt and type the following nslookup server 216.255.200.122 www.johnhappy.com ->Returns ->Server: happynt.housekeeping.com ->Address: 216.255.200.122 -> ->Name: www.johnhappy.com www.housekeeping.com -> www.housekeeping.com ->Server: happynt.housekeeping.com ->Address: 216.255.200.122 -> ->Name: happynt.housekeeping.com ->Address: 216.255.200.122 ->Aliases: www.housekeeping.com www.google.com -> www.google.com ->Server: happynt.housekeeping.com ->Address: 216.255.200.122 -> ->Non-authoritative answer: ->Name: www.l.google.com ->Addresses: 66.102.7.147, 66.102.7.99, 66.102.7.104 ->Aliases: www.google.com I did the sample of www.google at the end to show you what a normal response looks like. This is how your www.housekeeping.com comes back. There looks like there's something different between the two domains that's not returning the address when you're looking up the www.johnhappy.com. I think you're missing your alias record pointing back to either the johnhappy domain or the record containing the servers IP address. That is, you should be able to go to johnhappy.com or www.johnhappy.com and get to your web site. Seeing as you don't want to give your server's name away, I'd simply make a record called www in the zone and point it to the servers address. The domain needs to point there as well, so you create a blank or a period A record (I can't remember which) that points to the same IP. See if that helps you out. I think your host headers are probably correct, especially considering that you've done that part a lot before. Oh yeah, I also did a dnsstuff.com lookup on your domains. You need to turn off recursion on your domain servers (http://technet2.microsoft.com/WindowsServer/en/library/e1fe9dff-e87b-44ae-ac82-8e76d19d9c371033.mspx?mfr=true), and whomever the server at 216.255.196.186 is, it's not serving out DNS for you. It's probably not a problem since you're trying to get the secondary dns in house. There are other warnings like turning up your SOA refresh, changing your serial number, changing the SOA expire time, and no SPF record, but you can fix these once you get the site working properly. Hope this helps you, Don
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following