Questions

So, I changed ISP and Changed DNS providers... Now ADDNS is not resolving.

Tags:
+
0 Votes
Locked

So, I changed ISP and Changed DNS providers... Now ADDNS is not resolving.

XnavyDK
I almost had it all fit in the title.

Anyway. I changed ISP, and then added open dns as my dns, Changed the firewall to point to them, changed DNS in my dns server A records to point to OPen DNS, My computers are all jacked up, wont resolve. DHCP address that expire wont renew to the scope, 1-150 and DHCP assign numbers past the scope and i have to assign a static to make it work temp till I figure what I screwed up and where. Last resort is to restore from backup. I hate that. Somewhere i jacked up the DNS and I would rather learn how to fix it than do a restore. So Far, i have not a clue what I did, other than come up with the assign a static to work around it.
  • +
    0 Votes
    Seonix

    When you say you've [q] "changed DNS in my dns server A records to point to OPen DNS" [/q] what exactly are you referring to?
    Just so we're clear, can you explain end-to-end how your network is setup? For example, are you using your router as your DNS server or do you have an internal DNS server that you're trying to point to OpenDNS?

    +
    0 Votes
    XnavyDK

    Internal DNS and firewall is pointed to opendns. The DNS appeared to be pointed to my old ISP, and the DHCP was pointed to it as well. What I wanted to accomplish was point everything to open dns so I can see what we are doing on a scale. My new ISP has DNS but I wanted to have more control. According to what I m reading, I should have restarted the service once I made changes. I am going to restore from backup and document this time and check what ip's were what. Rooky mistakes are learning mistakes I guess. Thanks for your reply.

    +
    0 Votes
    Seonix

    You should (in theory) just need to do the following:
    - Configure DHCP assigned leases to point to your internal DNS
    - Restart DHCP server service
    - Configure internal DNS to use OpenDNS either by configuring it as the secondary DNS server, exclusive roothints server or by conditional forwarding.
    - Restart DNS server service, flush the cache and flush the cache on your test workstation/client.
    - Ensure firewall isn't going to block the port or address.

    That should be all you need.

    +
    1 Votes
    seanferd

    Nothing should point to OpenDNS resolver addresses except your DNS forwarders. Everything else should point to your DNS server, or you are going to break local name resolution. Delete root hints if you plan on using OpenDNS consistently, or at all.

    "changed DNS in my dns server A records to point to OPen DNS,"

    This sounds like a horrible mistake. Don't do this.

    "The DNS appeared to be pointed to my old ISP"

    You flushed all browser and local resolver caches, yes? No machines are pointing anywhere other than your DNS server for forwarding, right?

  • +
    0 Votes
    Seonix

    When you say you've [q] "changed DNS in my dns server A records to point to OPen DNS" [/q] what exactly are you referring to?
    Just so we're clear, can you explain end-to-end how your network is setup? For example, are you using your router as your DNS server or do you have an internal DNS server that you're trying to point to OpenDNS?

    +
    0 Votes
    XnavyDK

    Internal DNS and firewall is pointed to opendns. The DNS appeared to be pointed to my old ISP, and the DHCP was pointed to it as well. What I wanted to accomplish was point everything to open dns so I can see what we are doing on a scale. My new ISP has DNS but I wanted to have more control. According to what I m reading, I should have restarted the service once I made changes. I am going to restore from backup and document this time and check what ip's were what. Rooky mistakes are learning mistakes I guess. Thanks for your reply.

    +
    0 Votes
    Seonix

    You should (in theory) just need to do the following:
    - Configure DHCP assigned leases to point to your internal DNS
    - Restart DHCP server service
    - Configure internal DNS to use OpenDNS either by configuring it as the secondary DNS server, exclusive roothints server or by conditional forwarding.
    - Restart DNS server service, flush the cache and flush the cache on your test workstation/client.
    - Ensure firewall isn't going to block the port or address.

    That should be all you need.

    +
    1 Votes
    seanferd

    Nothing should point to OpenDNS resolver addresses except your DNS forwarders. Everything else should point to your DNS server, or you are going to break local name resolution. Delete root hints if you plan on using OpenDNS consistently, or at all.

    "changed DNS in my dns server A records to point to OPen DNS,"

    This sounds like a horrible mistake. Don't do this.

    "The DNS appeared to be pointed to my old ISP"

    You flushed all browser and local resolver caches, yes? No machines are pointing anywhere other than your DNS server for forwarding, right?