M
Marlon Brown
Sometimes I do
nslookup and it returns
myhost.domain.com
IP:1.1.1.1
Then I do
nslookup 1.1.1.1
and it returns:
somebodyelsehost.domain.com
In my Win2003 DNS server, I go to the "Reverse Lookup" zone and I see that
for such "1" subnet, I have *three* entries, same IP address pointing to
different hosts. That explains.
I see that "scavenge stale records" = 7 days.
Question here:
1) Imagine I have wireless users that walk by and leave. I also have VPN
users that simply shutdown the laptops and leave (not even logging off from
wireless).
Is that true that wireless and VPN that are not "gracefully" disconnected
would let the DNS records left in DNS ? When you shut down a windows (or
wireless) is that supposed to 'flushdns" records ?
2) What's the best way to avoid such duplication of records pointing to same
IP address ? Should I decrease the "Scavenge stale records" for how many
days minimum ?
nslookup and it returns
myhost.domain.com
IP:1.1.1.1
Then I do
nslookup 1.1.1.1
and it returns:
somebodyelsehost.domain.com
In my Win2003 DNS server, I go to the "Reverse Lookup" zone and I see that
for such "1" subnet, I have *three* entries, same IP address pointing to
different hosts. That explains.
I see that "scavenge stale records" = 7 days.
Question here:
1) Imagine I have wireless users that walk by and leave. I also have VPN
users that simply shutdown the laptops and leave (not even logging off from
wireless).
Is that true that wireless and VPN that are not "gracefully" disconnected
would let the DNS records left in DNS ? When you shut down a windows (or
wireless) is that supposed to 'flushdns" records ?
2) What's the best way to avoid such duplication of records pointing to same
IP address ? Should I decrease the "Scavenge stale records" for how many
days minimum ?