DNS servers configuration after AD/DC replication.

Good day all.
I understand that this issue might have been repeated several times in the previous posts/questions but nevertheless I feel the need to explain the situation I have thoroughly in order to have the right answer.
In our company, we have a W2k3 DC that has a DNS server installed with it. All clients (who happen to have a static IP, subnet, gateway and DNS) use this DC for internal DNS resolution. The hardware on this DC is getting old and we are planning to use it
to run an application that acts as a middleware between the machines that we have and our information system.
In order to achieve this goal, I suggested that we buy new hardware and perform replication of AD. According to my understanding of such a procedure, I know that we have to "upgrade" the forest that the w2k3 holds to be compatible with w2k8 and
after that we can perform DCPROMO, etc.
My question is: What happens to the DNS server on the old DC after I successfully perform the replication of AD on the new hardware and demote the old DC? It seems to me that I should keep the DNS server there running in order to prevent the action of manually
changing the IP settings for all clients in the network.
My other questions is: Should I create a replica for the DNS server as well ?
I appreciate the efforts made on TechNet and thank you for your time.
Nadim.

Hello Chris.Premo
I hope you are having a good day.
Allow me to describe my situation to you and if you may give me proper advice on what actions to perform.
1. We have a 2003 DC and a 2008r2 replica child DC. DNS on 2003 in primary pointing to itself and secondary pointing to the 2008r2. DNS on 2008r2 is the reverse (primary pointing to itself 'replica 2008r2' and secondary pointing to 2003DC)
2. FSMO roles are currently all held by the 2003.
3. DNS and active directory users and computers have successfully performed the replication when the 2008r2 was installed.
Goal: the goal here is to turn off the main 2003 DC and transfer its job and duties and roles to the new 2008r2.
I am in a situation where the IP of the old 2003 server cannot be changed and the machine itself has to stay online in order to serve other application.
What should I do ? How do i remove the active directory role and dns role from the server without letting it affect the domain and its functionality??
Please keep in mind that I am ready (and already started) to adjust the dns settings on all clients to point primary to the new 2008r2 (which is working) and secondary to our gateway (which in turn can forward the dns queries to my choice , which is in this
case the old 2003).
Thank you so much.
Nadim

Similar Messages

  • "No DNS Servers" error after 7.6 update

    After updating my Airport Extreme 4thGen to firmware 7.6 I recevied this "No DNS Servers error".  I did a restart of the modem then the Airport Extreme the problem is still there.  Please help.

    Crowhaven, did that work?
    I just updated firmware for my 5th gen Extreme, and got told that there were no DNS servers.
    I don't have a clue what a DNS server is.... (and why should I, I'm no IT expert!).
    I went into network settings, clicked on my 2Wire option (modem that used to do the wifi too) and found an IP address and some words.... it wouldn't let me type letters into the DNS box that came up with the warning, so I just typed some numbers in, which appear to be an IP address too.... it seemed to work.... I'm managing to post this.
    However, I have a feeling that I'll have problems later... :-)
    I'm running the latest version of Snow Leopard on a Mac Pro, 1st gen Intel.
    Anyone know what I should put in those two DNS boxes???

  • BUG in IMS 5.2 P 1 on Windows 2000 : not using the correct DNS servers

    Hi everyone,
    I encountered a queer bug in Ims 5.2 on Windows 2000.
    Let me explain it to all of you to avoid spending time and money debugging this problem.
    The problem may occur on Windows 2000 Server if the server used was formerly configured to obtain its IP address from a DHCP server (before using it for mail purposes).
    Windows 2000 doesn't delete its DHCP client configuration even if the machine is re-configured with a static IP.
    It stores the information in an interface registry key under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces
    If you install IMS52 after this, the server will use the DNS servers configured in the DHCP configuration rather than the ones specified in the static IP config to lookup the MXs.
    So if the nameservers configured in the DHCP config are not reachable, the smtp server will systematically fail sending outbond mails.
    To avoid this, locate the DHCP interface key in the Registry and remove it.
    Remarks :
    I know that this situation is not common but it may occur in certain occasions for people like me who are making demonstrations on clients sites.
    I'm not sure it is specifically related to DHCP rather than static config. I would say that IMS uses the first interface found in the registry (in alphabetical order) even if this interface is not active...
    A good idea is to remove completely from the registry all the interfaces keys not currently used by the system.
    Hope this will help some of you.
    Best regards,
    Vincent MAZARD
    DML FRANCE

    Interesting. Thank you for the observation. Not something I have seen, either.

  • DNS server configuration: dig @localhost myserver NXDOMAIN

    Hi, I've tried to look in all topics, but I was not able to find any solution.
    I'm installing a DNS service over a Mac OSX Server 10.6, but I'm still having lots of problems with the configuration.
    While the forwarders works greatly, the internal zone do not works:
    $ dig @localhost www.google.com
    ; <<>> DiG 9.6.0-APPLE-P2 <<>> @localhost www.google.com
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3652
    $ dig @localhost myserver
    ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 63100
    $ dig @localhost -x 192.168.0.202
    ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30287
    This is my configuration:
    $ hostname
    myserver.private
    $ ifconfig
    en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
    inet 192.168.0.202 netmask 0xffffff00 broadcast 192.168.0.255
    $ tail /etc/dns/options.conf.apple
    directory "/var/named";
    forwarders { 208.67.222.222; 208.67.220.220; 192.168.0.1; };
    allow-transfer { none; };
    $ tail /etc/dns/publicView.conf.apple
    acl "com.apple.ServerAdmin.DNS.public" {localnets;};
    view "com.apple.ServerAdmin.DNS.public" {
    //GUID=44FBB9A0-2F7F-4C09-ADD8-DD4615137B72;
    allow-recursion {"com.apple.ServerAdmin.DNS.public";};
    zone "private." {
    type master;
    file "db.private.";
    allow-transfer {none;};
    allow-update {none;};
    zone "0.168.192.in-addr.arpa." {
    type master;
    file "db.0.168.192.in-addr.arpa.";
    allow-transfer {none;};
    allow-update {none;};
    zone "." {
    type hint;
    file "named.ca";
    zone "localhost" IN {
    type master;
    file "localhost.zone";
    allow-update { none; };
    zone "0.0.127.in-addr.arpa" IN {
    type master;
    file "named.local";
    allow-update { none; };
    $ tail /var/named/zones/db.private.zone.apple
    $TTL 10800
    private. IN SOA myserver.private. admin.private. (
    2009111407 ;Serial
    86400 ;Refresh
    3600 ;Retry
    604800 ;Expire
    345600 ;Negative caching TTL
    private. IN NS myserver
    myserver IN A 192.168.0.202
    $ tail /var/named/zones/db.0.168.192.in-addr.arpa.zone.apple
    $TTL 10800
    0.168.192.in-addr.arpa. IN SOA myserver.private. admin.private. (
    2009111403 ;Serial
    86400 ;Refresh
    3600 ;Retry
    604800 ;Expire
    345600 ;Negative caching TTL
    0.168.192.in-addr.arpa. IN NS myserver.private.
    202.0.168.192.in-addr.arpa. IN PTR myserver.private.
    Does anybody have any suggestion ?

    Thanks Felix for quick response.
    In your scenario:
    1. You configured to different DNS servers and probably only one of them replied to DNS queries. And this is OK.
    2. When non valid IP configured means that DNS server will not reply to DNS query and than failover will query the second DNS server in the list. And this is also OK.
    I'm looking 2 different DNS servers configuration when one of them will reply to different domains. For example:
    First server will reply to *.mycompany.com.
    The second one will reply to any query except mycompany.com domain(since it is not published).
    Thanks again,
    Oleg.

  • DNS server configuration and behaivour

    Hi all,
    I'm looking for detail explanations which can explain how Mac OS X 10.6 *DNS client* works and may be configured.
    According to http://discussions.apple.com/thread.jspa?threadID=2227251 nothing is not guaranteed like order and failover.
    According to http://support.apple.com/kb/HT4030 failover will take affect when DNS server returns with SERV_FAIL (0x2) error code. What about NXDOMAIN (0x3) error code (which is more interesting scenario)?
    What I'm looking for DNS client?
    I'm looking for several DNS servers configuration which allow to split DNS domains for several areas. This, for example, may be very useful for VPN connections when VPN DNS server will resolve internal resource and another server (configured before VPN tunnel established) will resolve external resources.
    Is there any possible configuration to achieve this requirement for Mac OS?
    Thanks in advance,
    Oleg.

    Thanks Felix for quick response.
    In your scenario:
    1. You configured to different DNS servers and probably only one of them replied to DNS queries. And this is OK.
    2. When non valid IP configured means that DNS server will not reply to DNS query and than failover will query the second DNS server in the list. And this is also OK.
    I'm looking 2 different DNS servers configuration when one of them will reply to different domains. For example:
    First server will reply to *.mycompany.com.
    The second one will reply to any query except mycompany.com domain(since it is not published).
    Thanks again,
    Oleg.

  • Fetching the DNS servers

    Hi
    In java version 1.4
    How can i get the list of the DNS servers configured on my operating system?
    And how can I change the current (primary) dns server the InetAddress class is resolving the hosts with to another one?
    Thanks

    [root@solaris ~]# cat /etc/named.conf
    options {
    directory "/var/named"; # Working directory
    pid-file "named.pid"; # Pid file in working dir
    dump-file "/var/named/data/cache_dump.db";
    statistics-file "/var/named/data/named_stats.txt";
    memstatistics-file "/var/named/data/named_mem_stats.txt";
    * If there is a firewall between you and nameservers
    * you want to talk to, you might need to uncomment the
    * query-source directive below. Previous versions of
    * BIND always askedquestions using port 53, but BIND
    * 8.1 uses an unprivileged port by default.
    # query-source address * port 53;
    //zone "." {
    // type hint;
    // file "named.ca";
    zone "0.0.127.in-addr.arpa" {
    type master;
    file "named.local";
    notify no;
    logging {
    channel default_debug {
    file "data/named.run";
    severity dynamic;
    [root@solaris ~]# mkdir /var/named
    [root@solaris ~]# mkdir /var/named/data
    [root@solaris ~]# svcadm enable /network/dns/server:default
    Now you have you own DNS server

  • Configuring DNS servers with PPPoE

    Hi all,
    just received my base station, I'm trying to configure a custom couple of dns servers ( usually I work with opendns instead of the default ones from my ISP ) but after checking I notice that base station is still working with the default dns of my ISP. I tried to reset and re-configure the PPPoE connection but it still doesn't work.
    Any suggestion?

    Hello again, I feel sort of annoying by posting so many things. 
    I created a user in DC3 and it was replicated to DC1-New. If I do it the other way around, it does not work.
    In other words, the replication process only works this way DC3 --> DC1-New. I have checked it is not a firewall issue, all are off, since I began this lab.
    If I run repadmin /showrepl in DC1-New ,
    it sees DC3 and all success messages regarding the replication.
    If I run repadmin /showrepl in DC3,
    it just sees nothing.
    I also run dcdiag /test:knowsofroleholders in DC3 and
    there is this message: The holder of the Schema master is a deleted DC (DC1) . The same of all the 5 FSMOs. 
    I am trying to find a way to tell DC3 that the FSMOs holder is not DC1, but DC1-New. 
    Thanks for your support.
    Luis Olías Técnico/Admon Sistemas . Sevilla (España - Spain)

  • Order of DNS servers when using DHCP random after 10.9.3 update

    I am operating my local DNS server on my home network for resolving all local IP addresses and names.
    The router which connects me to the ouside world is also running a DHCP server serving the local network.
    It inherits from outside world two DNS server IP addresses (which cannot be disabled) and has the local DNS server
    manualy configured to be "first". I.e. it supplies via DHCP option 6 an ordered list of three DNS servers.
    So far so good and all was working well until the 10.9.3 update...
    I.e. the local DNS was on top of the list and the others where only queried when it was not responding for some reason.
    After the 10.9.3 update every time I do a DHCP renewal the list of DNS servers has a different (random) order.
    Not surprisingly if the local DNS isn't on top local lookups will fail.
    I have done some packet analysis on the LAN and the DHCP is definitely sending the DNS server IP addresses in the correct order
    (see rfc 2132, chapter 3.8).
    So why does 10.9.3 get the idea that it has to re-shuffle the order? To "improve the experience"???
    And more importantly hot to get rid of it and restore normal behaviour?

    This may be a bug. Send a bug report: Bug Reporting - Apple Developer. You can also report it via Apple Feedback, but the first link is better.

  • Configuring airport DNS servers

    I use an airport extreme base station which connects to the internet via an ethernet DSL connection. The airport TCP/IP settings are DHCP. The DNS servers, however, show 192.168.1.1 and not the DNS settings of the DSL. As a result the internet connection on my MacBook Pro is patchy at best with some pages that open and images not showing up. The only way I resolve this is by manually setting the DNS servers in my settings on the laptop. I have tried manually setting the DNS configuration on my Airport but for some reason this does not broadcast to all the computers in my house. The DNS settings that do appear on computers are the standard 192.168.1.1 and not the actual DNS. I cannot seem to figure out why the airport is doing this. Any suggestions would be appreciated.

    I am also wondering if it is possible to turn DNS relay off on an Airport Extreme or Airport Express. I am using the latest firmware on both devices, 7.6.1 and they are the latest model.
    Regarding your question about DNS servers; the IP address that shows in your device as a DNS server is the Airport Extreme LAN IP address. DNS queries will be sent to that device, and the DNS settings which it uses will be used to look domain names up.
    So, for now, put the DNS server addresses you'd like to use on your Airport Extreme. This is done through the Airport Utility, under Internet > Internet Options.
    Also, as a final note, try the ' namebench ' program to find the best DNS servers available. It helped me choose ipv4 dns servers and I'm noticing a difference in loading times.

  • Domain Controllers that are DNS servers DNS Client settings

    [Copying verbatim from a mail by Joe ]
    So I have been pinged by a few folks recently on configuration of client DNS settings on Domain Controllers that are also functioning as DNS Servers. Lots of debate. I understand there has been long time debate within MSFT as well.
    From http://blogs.technet.com/b/askds/archive/2010/07/17/friday-mail-sack-saturday-edition.aspx there
    is the quote
    "3.When referencing a DNS server on itself, a DNS client should always use a loopback address and not a real IP address."
    From http://www.microsoft.com/en-us/download/confirmation.aspx?id=9166 (Windows
    Server 2008 R2 Core Network Guide)
    "9.        In Preferred DNS server, type the IP address of your DNS server. If you plan to use the local computer as the preferred DNS server, type the IP address of the
    local computer.
    10.       In Alternate DNS Server, type the IP address of your alternate DNS server, if any. If you plan to use the local computer as an alternate DNS server, type the IP address of
    the local computer."
    From http://technet.microsoft.com/en-us/library/dd378900(v=ws.10).aspx (DNS:
    DNS servers on <adapter name> should include their own IP addresses on their interface lists of DNS servers)
    "The inclusion of its own IP address in the list of DNS servers improves performance and increases availability of DNS servers. However, if the DNS server is also a domain controller and it points only to
    itself for name resolution, it can become an island and fail to replicate with other domain controllers. For this reason, use caution when configuring the loopback address on an adapter if the server is also a domain controller. The loopback address should
    be configured only as a secondary or tertiary DNS server on a domain controller...
    Add the loopback IP address to the list of DNS servers on all active interfaces. The loopback IP address should not be the first server in the list."
    ESPECIALLY "For this reason, use caution when configuring the loopback address on an adapter if the server is also a domain controller. The loopback address should be configured only as a secondary or tertiary
    DNS server on a domain controller." and "Add the loopback IP address to the list of DNS servers on all active interfaces. The loopback IP address should not be the first server in the list."
    Why shouldn't loopback not be first, the justification is why you shouldn't only use loopback, not why it shouldn't be first.
    From http://technet.microsoft.com/en-us/library/ff807362(v=ws.10).aspx (DNS:
    DNS servers on <adapter name> should include the loopback address, but not as the first entry)
    "If the loopback IP address is the first entry in the list of DNS servers, Active Directory might be unable to find its replication partners. 
    The inclusion of its own IP address in the list of DNS servers improves performance and increases availability of DNS servers. However, if the DNS server is also a domain controller and it points only to itself,
    or points to itself first for name resolution, this can cause a delay during startup. For this reason, use caution when configuring the loopback address on an adapter if the server is also a domain controller. The loopback address should be configured only
    as a secondary or tertiary DNS server on a domain controller."
    This also seems like justification against only using loopback versus using it first.
    Are there any actual real documented issues for using loopback first and a remote DNS server second and perhaps third? If the local DNS server service isn't working yet (or at all), I would expect the DNS Client process
    to try to connect to it, fail, and then failover to the secondary just like I would expect it to failover if the remote DNS server was secondary and it was unavailable and it failed back to the loopback. Am I making a bad assumption?
    And by documented I don't mean random responses to questions on the internet or other such items. I mean a KB article or technet article or properly researched and tested other web article from a reliable resource.
    thanks, 
    joe

    As I understand it, the scenario whereby a DC could become an 'island' if it points only to itself, or to itself first, was repaired in the Windows Server 2003 product cycle. See
    http://support.microsoft.com/kb/275278 for information about this scenario.
    However, there is still a known problem of slow boot times that can occur. See
    http://support.microsoft.com/kb/2001093 for information about this. The scenario that is discussed assumes there is a power failure and servers shut down due to overheating while on backup power. When
    multiple servers come online simultaneously after power is restored, there can be a significant delay.
    The recommended configuration is one that avoids a single point of failure, but also tries to optimize the speed of resource record registration, so that Active Directory can properly synchronize.
    -Greg

  • DirectAccess 2012 has wrong DNS servers listed

    Hello,
    I'm setting up DirectAccess on Server 2012 and having issues with the wrong DNS servers continually added to the configuration. My setup is as follows, 2 Server 2008 R2 DCs running DNS, both have a static IPv4 and IPv6 addresses.  The DirectAccess
    server has a single NIC behind a NAT device and also has static IPv4 and IPv6 addresses.  My problem is that I keep getting a DNS: Not working properly error on the dashboard.  It says:
    Error:
    Enterprise DNS servers (fd7e:ed10:5cb6:7777::ac10:a22, fd7e:ed10:5cb6:7777::ac10:a21) used by DirectAccess clients for name resolution are not responding.  This might affect DirectAccess client connectivity to corporate resources.
    The thing is these are not nor ever have been the IP addresses of my DC/DNS servers.  I've removed them by using the configuration editor but with each restart of the server they reappear.  I examined the DirectAccess Server
    Settings GPO and they are listed in the Extra Registry Settings section buy I am unable to edit that portion.  I've read other threads on this forum that state I need to add the IPv6 address of the DA server as the DNS server but I still get DNS errors
    when I do that and after a restart the same two DNS servers show up again.
    Anyone have any ideas?  Your assistance is greatly appreciated.

    Hi,
    Thanks for you reply and sorry for relying so late.
    Did you point the DNS server address to the IP address of the internal NIC? Maybe you can refer to the similar thread below:
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/df08fa06-d3fc-4ca9-b4a2-85824a10819a/direct-access-server-dns-error?forum=winserver8setup
    Best regards,
    Susie

  • Testing an ISA Server Rule, the recursive query to other DNS Servers test fails

    Hello,
    I am trying to configure the following infrastructure with ISA Server 2006 and two W2003 servers (called "Server1" and "Server2") . "Server1" is a domain controller, and in
    "Server2" is the ISA Server installed, which also has
    attached two network Ethernet cards, one called "Internal Ethernet Card", and the other one called
    "External Ethernet Card".
    The infrastructure would be:  "Internal Ethernet Card"---- ISA Server ----"External Ethernet Card"---"Router"----"Internet"
    "Internal Ethernet Card" manages the internal package traffic of the infrastructure, the network segment which belongs is isolated from what we could called the Outbound traffic, which is linked to a router. "Internal Ethernet Card" it`s
    a virtual network.
    "Internal Ethernet Card" feature configuration is the following:
    - IP address: 192.168.3.3
    - Subnet Mask: 255.255.255.0
    - DHCP Enabled: No
    - DNS Server: 192.168.3.1 (Must point to the DC "Server1" which has the DNS Service installed)
    - Default Gateway:  None  (because doesnt point to outside)
    - Primary WINS Server: 192.168.3.1  
    The "External Ethernet Card" provides, the outbound connection, and this card is connected to the physical router.
    It`s feature configuration is the following:
    - IP address: 192.168.1.50
    - Subnet Mask: 255.255.255.0
    - DHCP Enabled: No
    - Default Gateway: 192.168.1.1
    - DNS Servers: 192.168.3.1 (Must point to the DC "Server1" which has the DNS Service installed)
    After configuring the network cards, I create the following rule in the ISA Server to allow the traffic towards outside from the server and the clients which have joined to the domain:
    Action: Allow.  Protocol: DNS.  From:"Server2".  To : External.  Condition: All Users
    After applying the changes to update the configuration, I enter in the Dns Server of "Server1" and in the "Monitoring" tab, I run a "recursive query to other DNS Servers" but fails.
    Only works the "simple query against this DNS Server".
    I don`t know why fails, but I`m stucked on this issue, because in the "Server1" DNS Server, in the "domain forward IP address list", I have added two DNS addresses which work OK.
    I would appreciate some help to solve this issue.
    Thanks
    Regards 

    Hello Ms. Long, 
    Yes, you are right. In the Server1 is configured the DNS server, to use forwarders whose are set in the field "Selected domain`s forwarder IP address list", two DNS address numbers obtained from "Open DNS", which work well.
    There is no DNS Server linked to the External NIC.
    The Server1 belongs to a private network configured as "VMnet3", which it is set as follows:
    IP address: 192.168.3.1
    Subnet Mask: 255.255.255.0
    Default Gateway: 192.168.3.3
    DNS Server: 192.168.3.1
    I have tried to test your suggested idea:
    > set d2
    > google.com
    Server:  srv-dcfs-01.dominio.local
    Address:  192.168.3.1
    SendRequest(), len 42
        HEADER:
            opcode = QUERY, id = 2, rcode = NOERROR
            header flags:  query, want recursion
            questions = 1,  answers = 0,  authority records = 0,  additional = 0
        QUESTIONS:
            google.com.dominio.local, type = A, class = IN
    Got answer (113 bytes):
        HEADER:
            opcode = QUERY, id = 2, rcode = NXDOMAIN
            header flags:  response, auth. answer, want recursion, recursion avail.
            questions = 1,  answers = 0,  authority records = 1,  additional = 0
        QUESTIONS:
            google.com.dominio.local, type = A, class = IN
        AUTHORITY RECORDS:
        ->  dominio.local
            type = SOA, class = IN, dlen = 46
            ttl = 3600 (1 hour)
            primary name server = srv-dcfs-01.dominio.local
            responsible mail addr = hostmaster
            serial  = 41
            refresh = 900 (15 mins)
            retry   = 600 (10 mins)
            expire  = 86400 (1 day)
            default TTL = 3600 (1 hour)
    SendRequest(), len 28
        HEADER:
            opcode = QUERY, id = 3, rcode = NOERROR
            header flags:  query, want recursion
            questions = 1,  answers = 0,  authority records = 0,  additional = 0
        QUESTIONS:
            google.com, type = A, class = IN
    DNS request timed out.
        timeout was 2 seconds.
    timeout (2 secs)
    SendRequest failed
    *** Request to srv-dcfs-01.dominio.local timed-out
    As you can see highlighted in bold, the problem remains in the "recursive query to other DNS Servers" check.
    Maybe is better to put the issue on the "Windows Server General Forum" , because the issue has not nothing in common with the ISA Server, dont you?
    Thanks
    Best regards

  • If your Airport is connected but you can't surf, check your DNS Servers

    I just had 2 customers who upgraded their OS's to 10.6 and it stuck 2 DNS servers in their network settings, 65.106.1.196 and 65.106.7.196. Delete them and if your computer is set to DHCP, it'll acquire the correct DNS servers from your modem or router. You can find them in "Advanced".

    Finally got it fix and setup!
    How I did it:
    1) Turn on AEBS, press and hold on reset button for 5 sec.
    2) Turn off AEBS after its initialization. (only center light permanently ON)
    3) Turn on iMac.
    4) Remote all KeyChain files related to AirPort. AEBS is still off.
    4) Update AirPort software to v4.2
    5) Update AirPort Extreme card dirver to v1.0 (update 2005-001)
    6) Restart iMac and login then Turn on AEBS.
    7) Pop-up shows "Apple Network as980510" is found, click OK.
    8) Run AirPort Setup Assistant from Application/Utilities
    9) Update AEBS firmware to v5.7
    10) After AEBS restart successfully, fine its configuration accordingly.
    11) Set dial-up ISP parameters and click Update
    12) At iMac System Preferences>Network click 'AirPort' then 'Configure'
    13) At 'AirPort' tab, change 'By default join' to 'Preferred Networks' and choose the one defined at step 8.
    14) At 'Proxies' tab, checked 'Web Proxy (http)', 'FTP Proxy' and key in ISP's proxies according.
    15) Launch Safari and start surfing.
    Because I have missed out step 12-14, that causes me hours of troubleshooting and late night sleep. Finally.... it works and I'm confident it's solved. Hope it will help some of you out there! Cheers!

  • Airport not distributing DNS servers over network

    Hi everyone,
    I connect to the Internet over ADSL (ISP: Arnet Highway, Buenos Aires, Argentina) using PPPoE from my MacBook Pro.
    I have my ADSL modem connected to the Airport Extreme (802.11n) and distributing IP over DHCP just fine. Every device that joins the network obtains a valid IP.
    However, DNS servers aren't distributed by the router over the network. Every connected device has to be manually configured to set the DNS servers of my ISP to be able to resolve hosts, instead of 'asking' these addresses to the router, as it should be.
    Initially I thought there might be a problem obtainig the DNS servers from the ISP. So in the Airport Utility, in Internet / PPPoE settings, I've manually set my ISP's DNS servers, which should be distributed over the network to all connected devices.
    This doesn't happen, and every somebody new joins my wireless network I have to manually change the DNS servers for that connection which, as I'm sure you'll agree with me, can be quite annoying. Not to mention what would happen if my ISP decides to use dynamic DNS addresses.
    Thanks for any help you might provide.
    Cheers.

    Hello belbo,
    I connect to the Internet over ADSL using PPPoE from my MacBook Pro.
    Is your Macbook Pro Network configured to use PPPoE or DHCP?
    I have my ADSL modem connected to the Airport Extreme (802.11n) and distributing IP over DHCP just fine. Every device that joins the network obtains a valid IP.
    Is NAT enabled on the AE? Are the valid IP Address obtained from your ISP or from the AE?
    However, DNS servers aren't distributed by the router over the network. Every connected device has to be manually configured to set the DNS servers of my ISP to be able to resolve hosts, instead of 'asking' these addresses to the router, as it should be.
    When you setup the AE to use PPPoE did you enter a Domain Name or a DHCP Client ID?
    Initially I thought there might be a problem obtainig the DNS servers from the ISP. So in the Airport Utility, in Internet / PPPoE settings, I've manually set my ISP's DNS servers, which should be distributed over the network to all connected devices.
    The DNS servers listed in the AE aren't distributed to each Network Device but are only used to translate names into IP addresses when need by a Network Device.
    This doesn't happen, and every somebody new joins my wireless network I have to manually change the DNS servers for that connection which, as I'm sure you'll agree with me, can be quite annoying. Not to mention what would happen if my ISP decides to use dynamic DNS addresses.
    If your AE is distributing IP Address using DHCP and NAT then this should not be a problem but I'm not sure without more information about the questions I asked.
    Later.
    Buzz

  • How do you setup a server to use multiple DNS servers that are not connect to each other?

    Is there a way to setup a server that connects to two different domains to use the proper DNS server for name resolution?
    Let say there are two DCs: serverA.subdomaina.domain.com and serverB.subdoamainb.domain.com.  The domains are independent and not connected.  Now you need a common server that is connected to both and need to resolve names from both
    domains.
    Is this possible?
    I have setup a server in a workgroup.  One NIC has the subdomaina.domain.com connection specific suffix and the other nic has the subdomainb.domain.com.  Each NIC has the DNS server listed for the domain it is connected to.
    This configuration will resolve FQDNs of one domain but not the other.  This I believe is due to the fact the server only querys one DNS server and doesn't try the other DNS server.
    Is there any way to make the server try another DNS server, if the first one doesn't have the entry?

    Hi,
    Thank you for posting in Windows Server Forum.
    Here adding to the words of “Tim”, a forwarder is a DNS server on a network used to forward DNS queries for external DNS names to DNS servers outside of that network. You can also forward queries according to specific domain names using conditional forwarders.
    A DNS server on a network is designated as a forwarder by having the other DNS servers in the network forward the queries they cannot resolve locally to that DNS server. You can refer information regarding forwarders and how to configure from beneath link.
    Understanding forwarders
    http://technet.microsoft.com/en-us/library/cc782142(v=ws.10).aspx
    Configure a DNS Server to Use Forwarders
    http://technet.microsoft.com/en-us/library/cc754941.aspx
    Hope it helps!
    Regards.

Maybe you are looking for