[AccessD] New server doesn't get domain name resolution

jwcolby jwcolby at colbyconsulting.com
Fri Oct 1 09:54:09 CDT 2010


Mike,

It just started magically working when I rebooted the router and the machine.

John W. Colby
www.ColbyConsulting.com

On 9/30/2010 1:12 PM, Michael Bahr wrote:
> John, did you do a port forward in the router and the range of ports?
>
> Mike
>
>> I built a new server last night and installed Windows 2003.  I was on the
>> internet, I installed
>> about 90 updates to Server 2003.
>>
>> Today I can ping ip addresses but I cannot ping the domain name, iow
>> Google is 66.249.92.104.  In
>> Firefox (or in ping) I can see that number but I cannot see Google.com.
>>
>> I have told the local area connections / tcp/ip properties to use 4.2.2.1
>> and 4.2.2.2 as my DNS
>> server but for some reason the translation request doesn't seem to leave
>> my LAN.  My router is what
>> does my local DNS and I can directly ping another computer in my network
>> by name, but I can't ping
>> out to the internet by name.  Just for the newest server though.
>>
>> Is there some way to tell my router that my new server exists and it needs
>> this stuff.
>> --
>> John W. Colby
>> www.ColbyConsulting.com
>> --
>> AccessD mailing list
>> AccessD at databaseadvisors.com
>> http://databaseadvisors.com/mailman/listinfo/accessd
>> Website: http://www.databaseadvisors.com
>>
>
>



More information about the AccessD mailing list