Crimsoneyes
MIS
I just migrated our network to W2K3 Domain Controllers, DNS, and DHCP.
I read up about turning on scavenging in DNS from Microsoft's site and it seemed like a good idea. Problem is, I came in this morning and a DNS record I needed got deleted/scavenged somehow and I had to manually recreate it. After further investigation, I found several DNS records for workstations all gone. This makes me think the scavenging feature isn't such a smart move. I had the settings set to 7 days for both non-refresh and refresh interval, but have turned all that back off as of this morning.
Another problem that has happened twice now since my migration is, for some reason my servers and clients will start trying to resolve internal names externally. Example: My exchange server is called smfr-ex01 @ 10.30.51.9. When things are working as they should, when you ping smfr-ex01 it should return 10.30.51.9. Twice in the last couple weeks, I've had users call stating their email wasn't working. When I try to ping smfr-ex01, it returns 65.38.170.90, our external web address! I also notice many of our other internal servers all trying to resolve to this same external address. I have not been able to track down why this is happening. All the servers are pointing to the correct Primary and Secondary DNS servers. I end up having to do a /flushdns and /registerdns to get the servers back on track again.
The only thing I can think is, my Secondary DNS server is out of service right now. The Primary is in service with no errors in the event log. My Primary DNS server is listed in the first position in my IP settings on all the servers. Since my Secondary DNS server is offline till next week, I have now removed my Secondary DNS entry on my servers and just have the one Primary DNS server listed. Could my Secondary one being listed yet out of service be causing the servers to try and resolve to an external IP? I can find no entry in my internal DNS for 65.38.170.90 except for a "www" Host(A) record.
What are your thoughts on this?
Thanks.
"My actions are not revenge...they are punishment...
I read up about turning on scavenging in DNS from Microsoft's site and it seemed like a good idea. Problem is, I came in this morning and a DNS record I needed got deleted/scavenged somehow and I had to manually recreate it. After further investigation, I found several DNS records for workstations all gone. This makes me think the scavenging feature isn't such a smart move. I had the settings set to 7 days for both non-refresh and refresh interval, but have turned all that back off as of this morning.
Another problem that has happened twice now since my migration is, for some reason my servers and clients will start trying to resolve internal names externally. Example: My exchange server is called smfr-ex01 @ 10.30.51.9. When things are working as they should, when you ping smfr-ex01 it should return 10.30.51.9. Twice in the last couple weeks, I've had users call stating their email wasn't working. When I try to ping smfr-ex01, it returns 65.38.170.90, our external web address! I also notice many of our other internal servers all trying to resolve to this same external address. I have not been able to track down why this is happening. All the servers are pointing to the correct Primary and Secondary DNS servers. I end up having to do a /flushdns and /registerdns to get the servers back on track again.
The only thing I can think is, my Secondary DNS server is out of service right now. The Primary is in service with no errors in the event log. My Primary DNS server is listed in the first position in my IP settings on all the servers. Since my Secondary DNS server is offline till next week, I have now removed my Secondary DNS entry on my servers and just have the one Primary DNS server listed. Could my Secondary one being listed yet out of service be causing the servers to try and resolve to an external IP? I can find no entry in my internal DNS for 65.38.170.90 except for a "www" Host(A) record.
What are your thoughts on this?
Thanks.
"My actions are not revenge...they are punishment...