Dns server in solaris 10 issues

Hello,
I have configured /etc/resolv.conf with the following:
nameserver 8.8.8.8
"nslookup www.yahoo.com" works fine to get the IP, but "ping www.yahoo.com" failed with with unknown host.
Did I miss something to configure my dns server?
Thanks for the help in advance.
Tom

You haven't configured a DNS server. You've told nslookup which DNS server to use to resolve a name to an address.
Try:
http://www.convery.me.uk/blog/?p=16
for assistance with your issue.
Don't forget that Solaris 10 uses both hosts and ipndoes. Later versions have these files linked together.
alan

Similar Messages

DNS Server Having Intermittent Issues with Open Directory

I work for a school and we're undertaking the large task of moving from Xserves running 10.6.8 to Mac Minis running 10.9. I have a lot of experience with OS X Server (I held ACSA up until they ditched it, and ACTC through the current OS) but I've hit a fairly large snag in configuring our DNS server. We currently run DNS via an AD server that is being retired at the end of the summer, so this is the first time our DNS will be Mac-based. That said, our network is ridiculously simple as we are a very small school. For the most part it's a flat network using the same IP range for our wired and wireless internal clients (we do have a vlan for guests but that's through Aerohive). I configured the DNS by hand, recreating the entries in our AD server (there were only about a dozen) and then adding in things that should have been there in the first place (e.g. printers and some other devices with static IPs that I'd like FQDNs for). Everything seemed to be working fine...until trying to log into Open Directory accounts.
For some background, the DNS server running 10.9 was the first server we upgraded and it was a completely clean install. We run DHCP on another Mac Server currently running 10.6.8 and it does have the proper OD server listed. All DNS entries for the OD server match our current DNS server. The issue is that it's taking some users 5-6 tries to log in with their network accounts. The errors they receive range from the login window shaking to it stating the user cannot log in at this time. This seems to be worse on client machines running 10.9. but it's appearing on machines running 10.6.8-10.9.3.
In my troubleshooting, I found that if I log in as a local user to one of those machines and do a dig for the OD server the results vary, this is where it gets weird. For example, if I dig ourodserver.ourdomain.org it will sometimes return host not found or it will sometimes resolve. If I ping the same thing it will sometimes work (even after stating it cannot resolve the host) and it will sometimes fail. If I then try a dig for the .local (e.g. ourodserver.local) it also yields the same varied results. However, on every machine that I've tested if I then open a Finder window and navigate to the server via the "Shared" menu and connect I have no trouble connecting and then magically my digs and pings in terminal work. If I revert DNS back to point to our old Windows server the issue goes away. I have meticulously combed through that server many many times now and am not seeing any missed entries. Any idea what could be causing this?

You must have a working DNS service, and the server's hostname must match its fully-qualified domain name. To confirm, select the server by name in the sidebar of the Server application window, then select the Overview tab. Click the Edit button on the Host Name line. On the Accessing your Server sheet, Domain Name should be selected. Change the Host Name, if necessary. The server must have at least a three-level name (e.g. "server.yourdomain.com"), and the name must not be in the ".local" top-level domain, which is reserved for Bonjour.
The primary DNS server used by the server must be 127.0.0.1 (that is, itself) unless you're using another server for internal DNS. The only DNS server set on the clients should be the internal one, which they should get from DHCP if applicable.

DNS Server on Solaris 10

Hi. I'm trying to install DNS in a Solaris 10, But there is some strange and is that the inetd file is so short, and in the rc2.d directory isn't the S72inetsvc that is the file that start | stop -TCP services. I copied that file from another server and this is the message :
"starting internet domain name server.
inetd is now an smf(5) managed service and can no longer be run from the
command line. "
Any knows haw can I do to fix it?
Thanks.
Francisco Velasco

From my latest efforts ( any corrections or improvements would be appreciated)
Reconfigure Services
( from http://src.opensolaris.org/source/xref/sfw/usr/src/pkgdefs/SUNWbindr/postinstall )
Dnsint04> svcprop p option/ip_interfaces dns/server:default
all
dnsint04> svcprop p options/configuration_file dns/server:default
Dnsint04> svccfg s dns/server:default setprop options/ip_interfaces=IPv4
Dnsint04> svccfg s dns/server:default setprop options/configuration_file=/etc/named.conf
Dnsint04> svcadm refresh dns/server:default
Dnsint04> svcprop p option/ip_interfaces dns/server:default
all
dnsint04> svcprop p options/configuration_file dns/server:default
/etc/named.conf
Dnsint04> vi /lib/svc/method/dns-server
     Change server=/usr/sbin/named to server=/usr/local/sbin/namedInstall BIND
# mkdir /usr/named
# cd /var
# ln s /usr/named named
# mount /nfs/OS-INSTALL
# cd /opt/PATCHES
# cp /nfs/OS-INSTALL/Solaris/bind-9.5.0-P1.tar.gz /opt/PATCHES
# gzcat bind-9.5.0-P1.tar.gz | tar xvf
# cd bind-9.5.0-P1
# ./configure disable-threads
# make
# make install
.pwd
# vi /root/.profile     Add /usr/local/sbin to the PATH statement (/usrbin:/usr/sbin:/usr/local/sbin: )
Confirguing BIND:
-     when the software is finished doing the installation, you have to create the /var/named/ directory and /etc/named.conf file. Depending on what type of DNS server you wish to create:
Primary:
-     review the configuration on the DNSEXT01(secondary external DNS), DNSEXT02(primary external DNS), DNSINT01(primary internal DNS) or DNSINT02(secondary internal DNS) server. In short find one and copy over the /etc/named.conf and /var/named-int/.named.root /var/named-ext/.named.root.
-     Allow transfer from dnsint01 ( or the current primary ) by editing /etc/named.conf on that box.
-     Stop and restart named on the primary.
-     Start named on the new box
-     Watch /var/adm/messages on both primary and newbox for errors
-     You should start seeing the db files populating in /var/named-int and /var/named-ext on the new box.
Secondary
-     review the configuration on the DNSEXT01(secondary external DNS), DNSEXT02(primary external DNS), DNSINT01(primary internal DNS) or DNSINT02(secondary internal DNS) server. In short find one and copy over the /etc/named.conf and /var/named-int/.named.root. /var/named-ext/.named.root.
-     Allow transfer from dnsint01 ( or the current primary ) by editing /etc/named.conf on that box.
-     Stop and restart named on the primary.
-     Start named on the new box
-     Watch /var/adm/messages on both primary and newbox for errors
-     You should start seeing the db files populating in /var/named on the new box.

DNS server on Solaris 8

I am interested in using Solaris 8 as an DNS server. Any advise on how I can configure it. I am new to Solaris 8, so any step by step advise is greatly appreciated.
Thanks a million.

Hi,
I am sending the configuration for DNS. But before doing it take a printout and have a study and then do it. If you have any comments don't hesitate to contact me.
Thanks.
Mohammed Abid Ali,
[email protected]
Dubai, UAE.
=========================================
For example consider the following
Domain name     universe.com
DNS server name     wstsun
DNS clients     wstsun1, wstsun2, wstsun3,
wstsun4
note: Use syntax, dots and space carefully.
Steps to create DNS server
1.     Go to /etc directory and create a file called �defaultdomain� and enter DNS name (universe.com)
2.     Reboot server by using init 6.
3.     Go to /etc directory and create �named.boot� file.
4.     Go to /var directory and create �named� directory.
5.     Go to /var/named directory and create the following file
i)     named.local
ii)     named.hosts
iii)     named.rev
6.     Go to /etc/nsswitch.conf file and add �dns� before the hosts.
Example of each file
i)     example of �/etc/defaultdomain� file � universe.com
ii)     example of �named.boot� file
;named.boot file on the dnsmaster (wstsun)
;files required by in.named are located here
directory /var/named
; here are the names of the primary files.
primary     universe.com named.hosts
primary     0.0.127.in-addr.arpa     named.local
primary     0.200.200.in-addr.arpa named.rev
iii)     example of �named.hosts� file
;SOA rec
universe.com.     IN SOA wstsun.universe.com. root.wstsun.universe.com
19970332          ;serial number
21600          ;refresh every 3 hours
10800          ;retry every 3 hours
604800          ;expire after a week
86400 )          ;TTL of 1 day
;Name Servers
universe.com     IN NS wstsun.universe.com.
;Addresses
localhost          IN A     127.0.0.1
wstsun1          IN A     200.200.0.1
wstsun2          IN A     200.200.0.2
wstsun3          IN A     200.200.0.3
wstsun4          IN A     200.200.0.4
wstsun          IN A     200.200.0.10
;aliases
dnsmaster     IN CNAME wstsun.universe.com
Note: Include DNS server name and ip number in hosts list.
iv)     example of �named.local�
0.0.127.in-addr.arpa.     IN SOA wstsun.universe.com. root.wstsun.universe.com.
19970331          ;serial number
21600          ;refresh every 3 hours
10800          ;retry every 3 hours
604800          ;expire after a week
86400 )          ;TTL of 1 day
;Name Servers
0.0.127.in-addr.arpa.     IN NS wstsun.universe.com.
v)     example of �named.rev�
;SOA rec
0.200.200.in-addr.arpa.     IN SOA wstsun.universe.com. root.wstsun.universe.com.
19970331          ;serial number
21600          ;refresh every 3 hours
10800          ;retry every 3 hours
604800          ;expire after a week
86400 )          ;TTL of 1 day
;Name Servers
0.200.200.in-addr.arpa.     IN NS wstsun1.universe.com.
;Pointer records for 1,2,3,4,10
1          IN     PTR     wstsun1
2          IN     PTR     wstsun2
3          IN     PTR     wstsun3
4          IN     PTR     wstsun4
10          IN     PTR     wstsun
Note: Include DNS server name and ip number in records list.
After creation of DNS database files run �/usr/sbin/in.named� to verify �named� server is ready for queries. If �named� daemon finds any errors in DNS database files you can find in �/var/adm/messages� file. Correct the errors in respective files and run daemon after killing old daemon by using �kill� command. By using �nslookup� command verify whether DNS server is responding or not.
Note: if you want DNS server to act as a client create /etc/resolv.conf and make the entries about domain name and IP number.
Creating DNS client
1)     Go to /etc directory and create �resolv.conf� file.
2)     Go to /etc/nsswitch.conf file and keep �dns� in front of hosts.
i)     example of �resolv.conf� file
domain          universe.com
nameserver     200.200.0.10
Note: resolv.conf file contains the information about domain name and IP number in which clients are located. Use �nslookup� command to DNS server responding properly or not.

DNS server configuration on solaris 10

Please, can somebody give me the way, step by step to configure a DNS server on solaris 10. i want to have the directories and files that it is necessary to modify and the modification to have a domain name "deptech.lan" with ip adress of the DNS server 192.168.100.2.
thank

> Please, can somebody give me the way, step by step to
configure a DNS server on solaris 10. i want to have
the directories and files that it is necessary to
modify and the modification to have a domain name
"deptech.lan" with ip adress of the DNS
server 192.168.100.2.
>
> thankDo this in this way,
1. unconfig your system
# sys-unconfig
2. Then press " Y" after that it wil reboot..
3. Then it will start config.
4. you can see like that,
Network ( y/n)
Network Interfence ( acc. 2 ur NIC , e.g. rstl0 /nge0 etc..)
select it. If you have two NIC in your system. then you choose any one..
5. Enter your " Host name"
6. then system ip
7. Then some stpes wll appear, it shows,, DHCp, Enable Ipv6 etc.. select acc. 2 ur configartion.
8. Then it will appear ' name service"
then select " Dns"
9. Give your DNS server name
10 . enter " server ip "
then search domain ( enter acc. 2 ur config/ may leave blank)
N.B: for going next stages / contiues you have to use " F2" key..
then it will configured..
Let me know if its ok or for any problem..
Thanks
Partha

NIS+, DNS server, DHCP

I have installed Solaris 2.8 with all the patches on a PC. I installed NIS+ populating the tables from the files included into the folder /nis+files. Now I want to install DNS server for a small local network made up by two hosts: a Window2000PC and a Solaris 2.8 PC. I want to use DNS server of Solaris 2.8 to test the functionality of a DNS client of the PC. And after I want to install DHCP to test the same funcionality . I should like to make things step by step, first with DNS server and after with DNS server together to DHCP server too, both installed on Solaris 2.8, coexisting .
On the network i have another host ,a router, that gives me the acces to Internet
How do i install DNS server on Solaris 2.8, and DHCP server ? Can someone help me ?
Thank you in advance
Marcello

Hi Guys,
I want to thank all for the valuable information.
I thought of sharing my own comments.
I have two SunSparc Ultra10 machines. I want to network them together using a Linksys router (Cisco) so they could communicate and also to be able to access the Internet. I let the router to do the (DHCP) work, however; since the routher doesn't send hostname I always got 'unknown' and I need to have proper hostname to do my training work. So, I've read this page and I thought I could contribute the result of my work.
(assuming my hostname= sys41)
On Solaris 10, all what I did,
1. On /etc/hostname.hme0 .. I've added,
inet sys41
2. I've created /etc/nodename .. and added,
sys41
3. On /etc/default/dhcpagent .. added,
REQUEST_HOSTNAME=yes
actualy, it was there, I just removed the comment (#) and changed it from no to yes
and double checked that I have ,
PARAM_LIST=1,3,6,12,15,28,43
That's all, I didn't need to change anything else nor add any script file or anything.
The following files where not there on my Solaris10 machine,
/etc/init.d/network
/etc/init.d/inetsvc
On Solaris 9,
1. On /etc/hostname.hme0 .. I've added,
inet sys41
2. I've created /etc/nodename .. and added,
sys41
3. On /etc/default/dhcpagent .. added,
REQUEST_HOSTNAME=yes
actualy, it was there, I just removed the comment (#) and changed it from no to yes
and double checked that I have ,
PARAM_LIST=1,3,6,12,15,28,43
I had to add 15,6,28 on my Solaris 9
4. /etc/init.d/network
changed all 'unknown' to 'sys41' which is my hostname
5. couldn't find /etc/init.d/inetsvc !
Then I've deleted /etc/nodename on Solaris 9.0 and still worked fine ..
On Solaris 10, I've deleted /etc/nodename and it didn't work.
So, I guess for Solaris 10 /etc/nodename is very important .. For the Solaris 9, /etc/inet.d/network did the job !!
Hope my comments were helpful... Regards ..

Internal DNS server and NAT routing issue.

Hi -- I am not terribly experienced with DNS and I am running into an issue that I can't seem to resolve. My company.com DNS information is hosted by an outside ISP for email, web, etc... but I have configured an A record there to point to the public IP to my mac os x server (server.company.com).
We have a cisco router configured with one to one NAT from the public IP to the internal IP for our server in a 192.168.15.x subnet. The same router is running DHCP and and NAT on that subnet under a different public IP provided by our ISP.
Our server is running DNS with recursion and has a "company.private" zone set up for internal services and machine names. Thus, the server is accessible via "server.company.com" from the outside and "server.company.private" from the private LAN.
The problem is that I would like to be able to access some services simply via "server.company.com" both inside and outside the private network. Now, accessing the "server.company.com" services from the private lan does not work because the name resolves to the external IP and the external IP cannot be used internally due to NAT.
Is there a way to configure my internal DNS server to respond with the appropriate private address when receiving a query only to "server.company.com" and forward requests on for anything else on "company.com"?
I know that I could manually duplicate all entries for our domain from my ISP and host the same entries for internal clients, but it would be much easier to only have our server handle requests for itself. The server is running OS X Server 10.4.11.
Thanks

Is there a way to configure my internal DNS server to respond with the appropriate private address when receiving a query only to "server.company.com" and forward requests on for anything else on "company.com"?
Ordinarily, no. Once your server thinks it is responsible for a zone (e.g. company.com) then it will answer all queries for that domain and never pass them upstream. Therefore you'd have to replicate all the zone data, including all the public records, and maintain them both.
The one possible exception to this (I haven't tried) is to create a zone for server.company.com that has your internal address. In theory (like I said, I haven't tried this), the server should respond to 'server.company.com' lookups with its own zone data and defer all other lookups (including other company.com names since they're not in a zone it controls). Might be worth trying.

Can I install Solaris 8 against an NT4 DNS Server?

Does anyone know whether this is possible using a plain vanilla NT4 PDC installation, including DNS Server service and a standard Solaris 8 installation on an Ultra 5 Sun box? Both will be running on a class C IP address, 192.168.0.x
Is there anything special I need to set up on either box or should the Solaris box pick up the NT DNS service as if it was on another Unix box?
Thanks in advance,
Rob.

the Solaris box must be running, BIND 8.9.3 or later
...pre-req for win2k also
S.

Bind 9 DNS Server chroot cannot work on Solaris 10 u6 and u7

My Old verion "Solaris 10 x86 Generic_Patch_118844-30" can be run "Bind 9 DNS Server" in chroot mode.
And this is no any problem.
I have been try to use "Bind 9 DNS Server" in Solairs 10 x86 u6 or u7.
The result is not any problem.
But when I turn it run in the chroot mode. the "Bind 9 DNS Server" cannot run.
I have been manuelly run the named:-
/usr/sbin/named -c /etc/named.conf -t /chroot/dns -u named -f -g
The respond is :-
13-May-2009 02:17:46.623 starting BIND 9.3.6-P1 -c /etc/named.conf -t /chroot/dns -u named -f -g
13-May-2009 02:17:46.624 found 1 CPU, using 1 worker thread
13-May-2009 02:17:46.627 socket.c:3259: unexpected error:
13-May-2009 02:17:46.627 open(/dev/poll) failed: No such file or directory
13-May-2009 02:17:46.628 ./main.c:495: unexpected error:
13-May-2009 02:17:46.628 isc_socketmgr_create() failed: file not found
13-May-2009 02:17:46.629 create_managers() failed: unexpected error
13-May-2009 02:17:46.629 exiting (due to early fatal error)
Look like the bind 9 runing in the chroot mode after that cannot find /dev/poll
Even I use Bind 9 version 9.6.0, the result is same.
So, I don't sure the problem are the Bind 9 or Solaris 10 u6/u7
I try to continous install New verion Bind 9 in my old version Solaris 10.
THE Result is NO ANY PROBLEM in old version Solaris 10.
And I already bypass the SMF problem.
Anyone can tell me what the problem in solaris 10 u6/u7?

Looks like something reported similar bug:
[BIND fails to start|http://bugs.opensolaris.org/view_bug.do%3Bjsessionid=376e1152f0ddc75829ed1725542e?bug_id=6799867]
but I am somewhat puzzled why there is no follow up on the bug fixing.
Ok, I found the source (may be?):
From named:
http://src.opensolaris.org/source/xref/sfw/usr/src/cmd/bind/bind-9.3.6-P1/bin/named/main.c
    462 static isc_result_t
    463 create_managers(void) {
    464      isc_result_t result;
    465      unsigned int socks;
    466
    467 #ifdef ISC_PLATFORM_USETHREADS
    468      if (ns_g_cpus == 0)
    469           ns_g_cpus = ns_g_cpus_detected;
    470      isc_log_write(ns_g_lctx, NS_LOGCATEGORY_GENERAL, NS_LOGMODULE_SERVER,
    471                 ISC_LOG_INFO, "found %u CPU%s, using %u worker thread%s",
    472                 ns_g_cpus_detected, ns_g_cpus_detected == 1 ? "" : "s",
    473                 ns_g_cpus, ns_g_cpus == 1 ? "" : "s");
    474 #else
    475      ns_g_cpus = 1;
    476 #endif
    477      result = isc_taskmgr_create(ns_g_mctx, ns_g_cpus, 0, &ns_g_taskmgr);
    478      if (result != ISC_R_SUCCESS) {
    479           UNEXPECTED_ERROR(__FILE__, __LINE__,
    480                      "isc_taskmgr_create() failed: %s",
    481                      isc_result_totext(result));
    482           return (ISC_R_UNEXPECTED);
    483      }
    484
    485      result = isc_timermgr_create(ns_g_mctx, &ns_g_timermgr);
    486      if (result != ISC_R_SUCCESS) {
    487           UNEXPECTED_ERROR(__FILE__, __LINE__,
    488                      "isc_timermgr_create() failed: %s",
    489                      isc_result_totext(result));
    490           return (ISC_R_UNEXPECTED);
    491      }
    492
    493      result = isc_socketmgr_create2(ns_g_mctx, &ns_g_socketmgr, maxsocks);===========================> here. (notice the error message and the actual function called are not the same).
    494      if (result != ISC_R_SUCCESS) {
    495           UNEXPECTED_ERROR(__FILE__, __LINE__,
    496                      "isc_socketmgr_create() failed: %s",
    497                      isc_result_totext(result));
    498           return (ISC_R_UNEXPECTED);
    499      }
    500      result = isc_socketmgr_getmaxsockets(ns_g_socketmgr, &socks);
    501      if (result == ISC_R_SUCCESS) {
    502           isc_log_write(ns_g_lctx, NS_LOGCATEGORY_GENERAL,
    503                      NS_LOGMODULE_SERVER,
    504                      ISC_LOG_INFO, "using up to %u sockets", socks);
    505      }
    506
    507      result = isc_entropy_create(ns_g_mctx, &ns_g_entropy);
    508      if (result != ISC_R_SUCCESS) {
    509           UNEXPECTED_ERROR(__FILE__, __LINE__,
    510                      "isc_entropy_create() failed: %s",
    511                      isc_result_totext(result));
    512           return (ISC_R_UNEXPECTED);
    513      }
    514
    515      result = isc_hash_create(ns_g_mctx, ns_g_entropy, DNS_NAME_MAXWIRE);
    516      if (result != ISC_R_SUCCESS) {
    517           UNEXPECTED_ERROR(__FILE__, __LINE__,
    518                      "isc_hash_create() failed: %s",
    519                      isc_result_totext(result));
    520           return (ISC_R_UNEXPECTED);
    521      }
    522
    523      return (ISC_R_SUCCESS);
    524 }And in isc_socketmgr_create2():
   3384 isc_result_t
   3385 isc_socketmgr_create2(isc_mem_t *mctx, isc_socketmgr_t **managerp,
   3386                 unsigned int maxsocks)
   3387 {
<SNIP>
   3488
   3489      /*
   3490       * Set up initial state for the select loop
   3491       */
   3492      result = setup_watcher(mctx, manager);===============================>will call open() on /dev/poll.
   3493      if (result != ISC_R_SUCCESS)
   3494           goto cleanup;
   3495      memset(manager->fdstate, 0, manager->maxsocks * sizeof(int));
Other the above, I cannot really understand or help further. But I know it should fail in somewhere in setup_watcher() in socket.c.

DNS requests from Solaris 10 box to Bind/MySQL DNS server fail

We have some servers running solaris 9 and some running solaris 10. We also have a DNS server setup running BIND with the MySQL backend. When I query the DNS server from our solaris 9 boxes, they always work just fine. However, when I query the DNS server from our solaris 10 boxes, they always fail. Queries to other DNS servers from the Solaris 10 boxes work just fine - they only fail when being sent to this particular DNS server. Here's exactly what I'm doing:
ON SOLARIS 9 BOX:
bash-3.00$ nslookup google.com calo-sunset
Server: calo-sunset
Address: <IP_OF_DNS_SERVER>#53
Non-authoritative answer:
Name: google.com
Address: 64.233.187.99
Name: google.com
Address: 72.14.207.99
Name: google.com
Address: 209.85.171.99
ON SOLARIS 10 BOX:
bash-2.05$ nslookup google.com calo-sunset
*** Can't find server name for address <IP_OF_DNS_SERVER>: Non-existent host/domain
*** Default servers are not available
In the case of the SOLARIS 10 box, <IP_OF_DNS_SERVER> is correct - it knows the IP address of the DNS server, but apparently it doesn't recognize that it's actually a DNS server.
I am utterly perplexed by this. It seems to me that a DNS request is a DNS request, regardless of your OS. Clearly something is different from Solaris 9 to Solaris 10 though because the requests fail on all of our solaris 10 boxes, and they succeed on all of our Solaris 9 boxes. Incidentally, dig requests from the Solaris 10 box also fail, where they succeed on the Solaris 9 boxes.
I don't really know what other information I could offer that might be useful. If you have any information at all about this or ideas on what I might try to troubleshoot/fix it, I'd love to hear it. Thanks in advance.

First off, I am an idiot. I got this entire post backwards. The fact is that the DNS requests work swimmingly well on our Solaris 10 boxes. They fail on our Solaris 9 boxes. I don't know how I managed to read this post all of these times and not notice that I got that backwards. Nice.
In any case, I've found the problem. It was non-trivial to me because I am not terribly familiar with the inner-workings of DNS. To those who are, it may seem painfully obvious. To me it certainly was not.
The problem was that the DNS server (BIND 9 with MySQL backend) did not contain a reverse DNS entry for itself. Apparently this is a big problem for Solaris 9. I got a hint that this might be the cause when I turned on verbose debugging info when I ran nslookup (nslookup -d2). I had to add the PTR record for the DNS server itself. I don't know why Solaris 9 would require that a DNS server contain reverse DNS information about itself, but sure enough it does. As soon as I added that info, the Solaris 9 boxes were able to successfully query the DNS server. Very odd.
Anyway, I doubt anyone else will come across this problem, but if you do, now you know something that might fix it.
Edited by: dprater on Oct 7, 2008 8:09 PM

Why doesn't my airport express router issue proper DNS server address to DHCP clients?

I have an Airport express router (version 7.6.4). It was configured to connect to internet via a cable modem, acting as a router with NAT. This means it obtians WAN address from cable modem, and in LAN it assumes IP address 10.0.1.1 as a gateway, and issue IP address to my 4-5 wireless clients (MBA, iPads, PCs) vi DHCP.
However I recently encounter an issue, that the router no longer issues DNS server address obtained from Cable Modem(206.x.x.x) but instead tell every DHCP client to use router ip address (10.0.1.1) as DNS server. I was pretty sure before Dec 2013 it is issueing (206.x.x.x) to all DHCP clients.
Apparently now the Airport express is acting as a DNS server or as a DNS cache. This works sporadically and very often result in long DNS look up or DNS look up failure.
Is this a bug or is it supposed to do so? Any configuration can turn it off so Airport express will issue Cable modem obtained DNS server to DHCP clients?
My network otherwise works fine. for some of the Clients (e.g. one MBA) I configured DNS for it mannually and it's internet is working very smoothly.

But this will be a problem for my ipad and iphone that uses wifi.
These devices either allow full DHCP. If you need to mannually enter DNS server, you will need to turn entire IP configuration to mannual and that will be a problem for me.

Known Issue: "DNS server could not be reached" when creating or updating a RemoteApp collection using template images for some locales

When trying to create or update Azure RemoteApp collections that use a template image for some non-EN-US locales, it might fail with error "DNS server could not be reached". You might also see error code "DnsNotReachable".

Cause: There was a issue in Azure in which decimal punctuation was not treated properly if the locale of the template image used a comma (,) instead of a period (.).
Workaround: Before a fix was applied, the workaround was to use template images based on a locale that uses a period to delimit decimals, such as EN-US.
Resolution: As of March 19, 2015, a fix for this issue has been applied to Azure. You should once again be able to create collections from template images that use non-EN-US locales. If you continue to have this problem, please
try the workaround. If that works and the only difference in the template images is the locale, please email remoteappforum (at Microsoft). If the workaround does not work, the issue is likely caused by a DNS configuration issue such as:
No valid forwarders to public DNS servers configured on your internal DNS server(s).
A valid internal DNS server is not specified on your Azure RemoteApp VNet.
A VNet or internal network configuration issue is preventing the internal DNS servers from be reached by the VMs in the RemoteApp collection.

DNS Server does not resolve new generic Top Level Domain names- CNR configuration issue?

Hi all,
I am not sure if this is the correct community to post this question, but I will give it a try. I noticed that the users of my network cannot resolve web sites using new top level domain names, like ".education", ".international", etc. I have an internal DNS server made by Infoblox and a Cisco CNR v6.3.3.1 as an external DNS server. Infoblox uses CNR as its forwarder and CNR uses the root DNS servers for queries.
I would think that CNR was the problem because it is an obsolete product but after speaking with a fellow engineer at another organization where they still use an older version of CNR than mine, they have no problems at all. So now I am thinking it is a setting either on Infoblox, or on CNR I need to change. I can see Infoblox is forwarding the requests to CNR but that's about it. I am not sure if CNR is discarding the request. When I do an nslookup from a PC in my network it does not matter if I set my DNS server to be the Infoblox or the CNR. Neither resolves the URL.
Then again, no matter what I lookup using the CNR as my DNS, I only get a response with the root DNS names and IPs!
Any help is appreciated!

Hi Constantinos,
Have you taken a look at the infoblox community site? We've just reposted your question there and alerted some internal SMEs that should provide a solution soon.
https://community.infoblox.com/forum/ddi/dns-server-does-not-resolve-new-generic-top-level-domain-names-cnr-configuration-issue
Best,
Eric

2nd DNS Server- Cause Issues on Main Network?

At work there is already a Windows 2003 Domain controller that serves up DNS and DHCP. I want to try and deploy iCal 2, which requires DNS, Open Directory and a FQDN name for my server.
I already have the DNS name. However, will configuring and running DNS cause any issues on the network with the other computers, which get their DHCP address and DNS requests from the Windows server? I'm not going to deploy DHCP, and thus, I won't be introducing a 'rogue' DHCP server on the LAN. However, I'd like to be sure I'm not going to disturb anything before I proceed.

having your own DNS server is not dangerous unless clients get that address. If you are not running DHCP on the new server your clients will not get that as their DNS.

DNS Server Issues with Comcast and Airport Extreme wifi routers

I am having significant challenges with 3 Airport Extreme (latest gen) wifi routers and my Comcast Xfinitity service. It once worked just fine, but now I continually get the blinking amber lights stating "No DNS servers" for each of the Airport Extreme (AE) routers. My configuration is:
Coax cable -> Comcast Xfinity cable modem -> ethernet to 16-port gigabit ethernet switch ->->-> ethernet to 3 Airport Extremes around the house direct connected with switch
I have many wifi devices throughout the house (iPads, MacBooks, home automation devices) as well as direct-connected devices via ethernet (one PC connected to AE router).
Each Airport Extreme router is set with these settings in the Airport Utility app:
Internet tab= Connect using: DHCP
Wireless tab= Network mode: Create a wireless network
Network tab= Router mode: Off (Bridge Mode)
I have attempted to put the Xfinity cable modem in bridge mode, and use the Airport Extreme to serve up the IP addresses, but still lost internet connectivity.
I have also attempted to set the Network tab=> Router Mode to "DHCP and NAT" but get "Double NAT" error issues as well.
I have tried using the Comcast DNS server addresses (75.75.75.75;75.75.76.76) setting on the Internet tab for the routers and do end up getting a green light, but NO internet connectivity.
Lastly, I have tried using the Google DNS servers (8.8.8.8;8.8.4.4) setting on the Internet tab the routers giving me the No DNS servers amber light error and again, no Internet connectivity for either wifi-connected or even ethernet connected (directly to Airport Extreme router) devices (like my PC) despite getting a green light on the router.
Any this point, it really seems that these AE routers are NOT compatible with the Xfinity cable modem or service… (and yes, I've tried power-cycling and restarting the modem, and then the AE routers, MANY times to little avail).
Should I move one of these Airport Extreme wifi routers to before the switch, and have the other 2 in Bridge mode after the switch? Do I need to setup a specific range of DHCP reservation addresses for each different AE router?
Appreciate any insight anyone can share with this aggravating DNS server issue between Comcast & multiple Airport Extreme wifi routers.

I do not see anything wrong with your basic setup.. the issue is indeed the WAN ports of the AE.. AC version are having problems with some network equipment.
You have listed a stack of things you have tried.. but I want you to move the ethernet patch cable you use on each AE to its LAN port instead of WAN.
Restart the airport when you do that.. and then see if it becomes stable.
In bridge mode the airport moves the WAN port to LAN.. but the WAN port setup itself seems more problematic than the LAN ports.
There are other methods we can try if this does not work.. but in the end.. I would be tempted to take the whole lot back to apple.. they need to start making equipment that works with standard modems and switches.
BTW what brand is the 16 port switch?? Does it happen to be managed (smart type)?

Dns server in solaris 10 issues

Similar Messages

Maybe you are looking for