[EMAIL PROTECTED] wrote: > Hello All,. > > Last night was the night for my market to transition from comcast@home to > comcast.net. I have a box setup with Suse7.2, suse-firewall2 as a router > and it uses dhcp to get it's IP address. I had to reboot for some strange > reason to find out the new IP and nameservers. I then immediately went to > change all my boxes (mix of Linux/Win9x) nameservers to the new one found > in resolv.conf, but nothing will forward. I went back to the old name > servers but with the new IP address via dhcp and things work as usual. > Detail: I am on the dalecty01.va.comcast.net domain, but the nameservers > are md.comcast.home.com or something ( I am at work now and don't remember) > Has anyone made the transition and if so, are your nameserver IP's working > right or did you have to use the old ones? >
I'm confused, how can you use a domain name for a nameserver (md.comcast.home.com), don't you need an IP address? Otherwise, how can you resolve the name of the nameserver? Mine's working fine using IP addresses: 68.34.76.5 68.34.76.6 Under @home, the nameservers were: 24.3.0.33 24.3.0.34 I'm in the Baltimore, MD area, if that matters... HTH, Tim _______________________________________________ Linux-users mailing list - http://linux.nf/mailman/listinfo/linux-users Subscribe/Unsubscribe info, Archives,and Digests are located at the above URL.
