Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We have our own internal DNS server inside our network on our domain. I just changed the nameservers of a bunch of our domain names through our registrar. Now on my home PC (off the network) the changes were almost immediate. How ever inside our network the changes are not immediate. In fact I went into my DNS Manager and I have a few of these domains setup as zones (not all of them) and I notice the records still have the old IP address of the old namespace, and the timestamp is STATIC. Will I have to manually edit these or can they somehow be automatically updated like everything else once the DNS has propgated on the internet.

share|improve this question

2 Answers 2

up vote 4 down vote accepted

If you are talking about the values in your DNS servers cache, you'll probably need to flush the cache on the DNS server.

If you have primary zones, these won't be updated automatically. You'll need to manually change these.

share|improve this answer
    
Ok I was given 3 namespaces for www.mydomain.com. I put them in my registrar. Do I need to put each one in my primary zone? Right now all I have is an IP address. Thank you! –  drpcken Jul 8 '11 at 23:26
    
Let me clarify a bit more: registrar is network solutions. host is dreamhost. In my internal dns there are static entries for www.mydomain.com whcih point to the ip address of network solutions (which i'm moving away from). On network solutions i changed my namepsace to dreamhosts (ns1.dreamhost.com, ns2, etc..). However in my DNS server I can't add FQDN for A records, only IP addresses. How can I accomplish this? –  drpcken Jul 8 '11 at 23:37
    
All you should need to do is double click on the A record for www and change the IP address to the new public IP address. If your web host and DNS host are dreamhost, you shouldn't need to have a mydomain.com zone in your internal DNS server. If you were to remove it (assuming you aren't using that domain for anything else) then it should just call the public DNS for the IP just like anyone else would. –  mrdenny Jul 9 '11 at 0:03
    
I see. Problem is this domain is also my internal domain name. I dont' think I can just delete it as a forward lookup zone. I may jsut have to add aliases to the dreamhost namespaces, or A records for the namespaces ip (but what if they change?).. –  drpcken Jul 9 '11 at 0:07
1  
Here's the TechNet document on how to rename your Windows domain. technet.microsoft.com/en-us/library/cc738208%28WS.10%29.aspx –  mrdenny Jul 9 '11 at 1:05

If the timestamp is static then I'm going to assume you entered them manually into your DNS server? If so you will need to modify them by hand.

From what I'm seeing in comments, you are making static A records for your domain inside which is the same outside (mydomain.com).

This is a common problem when creating a domain inside your network with a publicly addressable domain, this is why people have domains specified as .local to avoid the problems of using a .com inside their network. It's the same reason there are private ip ranges (192.168.0.0|172.16.0.0|10.0.0.0) so you avoid the problems of routing public ip addresses in and outside your network.

share|improve this answer
    
.local has been co-opted by auto-configuration by avahi (aka bonjour). Configuring .local in DNS can lead to namespace conflicts. .lan and other non-existent top level domain can be used internally. The upcoming ability to but TLDs may cause problems in the future. Reserving a sub-domain like lan.example.com for internal addresses may be a better option. –  BillThor Jul 9 '11 at 12:10

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.