Are you a Google Analytics enthusiast?
More SEO Content
Dns On Dsl Via Local Network Proxy...
Posted 05 April 2007 - 05:47 AM
I'll probably use the DNS on our server at a later date, but I'm not sure if it currently accepts requests in the way I want to do it, so to start with I thought it would be a good idea to find a free public DNS server to use while I figure out how this setup works. I found some, but can't get it to work.
First questions is, how can I tell that the public DNS server I'm trying to use is active and will accept my requests? I may be the eternal optimist, but I'm guessing it's possible that I set it up correctly and the DNS I'm trying just isn't working right now. (alternatively, can you reccomend one that you know is working?)
Second, if it is working, at what stage do I add the info to our setup? FYI I'm on a LAN behind a proxy. I tried adding the info to my local network connection and it didn't seem to have any effect. I then tried adding it to the DSL connection on the gateway PC and the connection stopped working. I reset both connections to automatically obtain DNS and it's all working fine again now - except, of course, that one domain whos nameserver I changed nearly a week ago is still pointing at the old server.
Thanks in advance.
Posted 05 April 2007 - 06:58 AM
Are the sites hosted on your ISP and they're not updating the DNS properly? If so, tweaking the TTL will probably help.
Or is the DNS actually changing when it should for the sites (check using something like DNSReport.com since they use real time lookups) but are simply not updating for you because of your ISPs DNS Cache?
If this is the problem you may be able to correct it by tweaking your hosts file in a Windows machine. On an XP Pro machine this file should be located at C:\Windows\system32\drivers\etc\
There should be some instructions at the top of this file. You'll want to make sure you edit it with a plain old text editor, like Notepad, and make sure it gets saved without any extension. The first line should always be 127.0.0.1 localhost. From there you can add others.
So if all of your domains are pointed to the nameservers ns1.somedomain.com and ns2.somedomain.com, and the IP numbers that correspond to those nameserver addresses are 184.108.40.206 and 220.127.116.11, and yourdomain.com is tied to IP number 18.104.22.168 your hosts file would end up looking like:
The above should allow your computer to forego using your ISPs DNS cache and go directly to the server.
Not sure that's the answer you're looking for, since I'm not sure I understand what's happening exactly.
Posted 05 April 2007 - 07:51 AM
The ISP, the domain registrar/host and the server host are three separate companies. The nameservers on the server are set up correctly, the nameservers associated with the domains have changed as they should and other people on other ISPs are able to see the sites as they should, it's just our ISP that is letting the side down.
Would changing this info in the hosts file avoid using the ISPs DNS for all domains? I have a load of different domains to deal with and am hoping to avoid the ISPs DNS altogether (as much as anything, I know I could do with a bit more experience and expertise with DNS)
Edited by rolf, 05 April 2007 - 10:20 AM.
Posted 05 April 2007 - 11:18 AM
I think I understand the logic and I suspect the problem may be that the IP for NS1 is the same as the IP for the domain I'm testing it on - would that explain it?
Posted 05 April 2007 - 02:23 PM
I mean, by default, you're set up to use your ISPs, but there's nothing stopping you from going into the network connection settings and changing your primary and secondary DNS to something else.
I'm sorry, Rolf.. I don't know anything about publically open DNS servers. I wish I did. Verizon's nameservers are slower than molasses to update, too.
Posted 05 April 2007 - 03:30 PM
If you have a router this can be set in the router configuration. If not you'll need to set it up in the main connection on whatever is functioning as your Gateway.
As far as what IP numbers to plug in for your DNS servers there are lots of approaches you can take. Since your server is running DNS you may be able to simply use those IP numbers. Though this is going to depend upon the firewall configuration on the server itself. My own servers won't allow that to cut down on the junk connections out there, cept I have a small hole in the firewall for me to use if I feel like it. For any domain that isn't on the server I then get forwarded out to the real DNS servers.
Or you may want to take a triip by OpenDNS.com. They provide IPs you can use to bypass your ISP completely. And there are instructions there showing how to set it up, depending upon how you currently connect to the 'Net.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users