Wrt54g not updating dyndns
Adding an entry to the host file definitely works, but I don't want to go around to each client and set that up.Nor do I want to explain to everyone how to edit the file due to the private IP address while on the office network and public address while outside the office network.Note that depending on how many DNS servers you have resolution by host name may not work until a zone transfer is initiated.Also note that if you have been trying to access the web site by the public host name, the resolver cache on your PC may need to be flushed by issuing ipconfig /flushdns and perhaps even nbtstat -RHope this helps. One thing that concerns me, though, is the fact that when I ping the name, it resolves the address just fine, but I get no response. I added the Forward Lookup but the results did not change. I am using the DHCP server on the Linksys router to assign IP addresses to the wireless clients.
if this is the case you'll need to make an entry in your internal DNS to point to the private IP address of your web server We are not using AD here.dyn DNS (dyn.com) doesn't offer any free version of their service anymore.Without using 3rd party firmwares: Is it possible to use other free DDNS services like no-ip for DDNS and if not, will there be an update soon that includes free DDNS hosts?I'm assuming that you are running XP clients, if so navigate in Windows Explorer to %windir%\system32\drivers\etc and find the file labeled hosts.Open it and follow the example given in the file to add this entry. You don't have any root zones "." configured do you?(I have flushed my client DNS using ipconfig /flushdns as suggested.) Some more info...If I do an nslookup on the DNS server for the public name of the web server it resolves to the private IP address (good).I am stumped with this problem, desperately looking for help... The Firebox is connected to our public internet connection, of course, and it's also connected to a wireless router (Linksys WRT54G - we have 5 users max in the office, typically only 1-3 on any given day).I've also got a server running Apache connected to the office network that needs to be accessible to the public.If I do the same nslookup on my wireless client, it resolves to the public IP address (bad).If I ping the public name of the web server from either the DNS server or the wireless client, it resolves to the public IP address and of course gets no response.