Please Read: Significant Update Planned, Migrating Forum Software This Month

See more
See less

Badly setup dns

  • Filter
  • Time
  • Show
Clear All
new posts

  • Badly setup dns

    I have just recently taken over looking after our company server. I have found that the previous IT expert (aka moron) has set up the server to use an external ip address (84.x.x.x) as both primary and secondary dns.
    I need to reset this to use our internal server address of 192.x.x.x (the x's are real numbers in our server of course).

    i believe i have to go to the network card, type in the new primary dns as 192.x.x.x but dont know what to use as secondary dns or do i leave this blank?

    i then go to cmd prompt
    is the following the correct way to go about this?

    ipconfig /releaseall
    ipconfig /flushdns
    ipconfig /renewdns

    do i need to use ipconfig /registerdns ?? or is this only when setting up a new dns server.

    If any one can check this and point me in the right direction i would be very gratefull

  • #2
    Re: Badly setup dns


    Please create IP list of all the servers/computers in the company.

    Change DHCP scope to the new DNS server and run:

    ipconfig /releaseall
    ipconfig /flushdns
    ipconfig /renewdns

    Change the IP settings of the internal server that use as DC and vertiy:

    1. The server can send DNS query (UDP Port 53) outside the company to the internet.
    2. Restart the DNS + Netlogon service on the DC. If you own
    SBS you will have "IP Change" wizard.
    3. Run DCDIAG + NETDIAG to verity correct work of the DNS server.


    Best Regards,

    Yuval Sinay

    LinkedIn:, Blog: