|reply to coxta |
Re: Crazy problem
said by coxta:
It's not quite that easy. You can't shut off the DHCP on the modem.
DHCP isn't magic. All you have to do is create a new subnet and then your router becomes the DHCP server for that subnet while the AT&T Uverse RG is only DHCP for it's subnet which would connect to the new router's WAN port.
The DNS is:
Which are anycast IP's valid anywhere. Or you can use any DNS you want it doesn't really matter honestly for internet traffic.--
My Blog. Because I desperately need the acknowledgement of others.
The Judd Family site!
Of course it isn't magic. Any DNS should do although the ISP's DNS may be faster depeneding on how that web page is routed. And as has been discussed, I can limit the DHCP to a different subnet from my LAN router.
Keep in mind that the installer should be able to set his modem up the way I request. I wasn't even able to get manual with the modem. I have one now and I have some other information, but we shall see how things go.
Well, I have some of the network up and working. I guess the last thing he did was try to use citrex to log on to a remote gateway.
I did forget to mention that I walked on in him as he was pulling the cables out of our router and switch. I guess he thought it was ATT's modem and other property. That's why only a portion of the network is up and running. He didn't plug them all back in as they should have been.
Well, the good news is that all seems to be working after a few hours of work. It's not particularlly fast, but I didn't run any speed tests. I will wait and see how stable it is over time. Thank you everyone (except for ATT unless some of you are ATT employees) for the assistance.
Numquam ponenda est pluralitas sine necessitate
In general, ATT's DNS is crap. I would avoid it if possible.
|reply to Paralel |
Unlike a lot of DNS servers out there, 68.94.156/7.1 both support DNSSEC. At least forward thinking...
So I disagree.