Routing DNS requests in a zone to a default host

Hi,
What I'd like to do is to direct all DNS requests for non-existent hosts to a single host by default. So even if I haven't defined a hostname in my zone, the request will still resolve (to this default host). Any ideas?
Ben

It's possible to do via wildcard DNS, but you cannot do it via Server Admin (it doesn't permit the * for the wildcard name), therefore you have to get under the hood and edit your zone file directly.
You'll need to find your zone's domain file in /var/named and add a line like:
* IN A 1.2.3.4
(where 1.2.3.4 is, obviously, the IP address you want all unknown addresses to point to).
You'll also need to increment the serial number in the SOA record near the top of the file (otherwise your change won't be noticed)
Restart named (e.g. via killall -HUP named or via Server Admin), and now any lookup for an unknown host will return the specified address.

Similar Messages

WRT1900AC: Can it block DNS requests?

Hello,
Can the WRT1900AC block DNS request from devices in a home network to public DNS service like GoogleDNS? Can anyone tell me what steps are necessary to accomplish this?
I tried to follow instructions found on the web but I could not add static routes under Advanced Routing, I got errors either about the network submask or the Gateway (mine is 192.168.1.1 and is not accepted). i don't know what to enter in these fields and also what Interface to select (LAN/Wireless or Internet).
My firmware version is 1.1.8.164461.
I would appreciate any help.
Thank you,
Luiz
Solved!
Go to Solution.

Hi,
Thanks for replying. I haven't contacted support yet to confirm you suspicion, My cable modem is a Motorola SB6141. I have done some basic research that indicates that it is not capable of NAT.
However, I was able to configure a static route in my router,using the cable modem IP asgateway. After this my ping requests to Google DNS (8.8.8.8 and 8.8.4.4) started to fail. This is probably still not what I need. I don't understand why I can't save my router's IP as gateway as indicated here: http://help.unotelly.com/support/solutions/articles/193662-setup-static-routes-on-linksys-and-cisco-... This link alerts to a bug in Linksys routers but the error message I get is not "invalid static route" as indicated.
Thanks,
Luiz

DNS request timed out. timeout was 2 seconds. *** Request to self timed-out

I am having an issue with one of my domain controllers (Server 2012 R2). It is a DNS server as well and it times out 100% of then time when attempting connect to either of the two trusted forests that are setup as conditional forwarders. There is also a
delay or a time out the first few times when attempting to resolve an external site such as google.com. The domain controller functions fine. All routing seems to fine, because I can telnet on port 53 to the trusted forest's DCs. They can even use the problem
DNS server to resolve hosts. It just does work from my controller to the other forest. Here is an example of what is happening.
> external.forest.dc
Server: problem.local.dc
Address: 192.168.1.8
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to problem.local.dc timed-out
> external.forest.dc
Server: problem.local.dc
Address: 192.168.1.8
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to problem.local.dc timed-out
Google will resolve eventually resolve
> google.com
Server: problem.local.dc
Address: 192.168.1.8
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to problem.local.dc timed-out
> google.com
Server: problem.local.dc
Address: 192.168.1.8
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to problem.local.dc timed-out
> google.com
Server: problem.local.dc
Address: 192.168.1.8
Non-authoritative answer:
Name: google.com
Addresses: 2607:f8b0:4006:808::1001
74.125.226.67
74.125.226.66
74.125.226.72
74.125.226.69
74.125.226.68
74.125.226.70
74.125.226.73
74.125.226.64
74.125.226.65
74.125.226.71
74.125.226.78
The other DC works as it should:
> external.forest.dc
Server: working.local.dc
Address: 192.168.1.7
Non-authoritative answer:
Name: external.forest.dc
Address: 10.1.1.1
There is a firewall between these networks, they connect via campus fiber. I created an any rule to rule that out. I am thinking the DNS server is corrupt, but I cannot figure it out.
Dcdiag /test:dns says everything is great.
Any suggestions?

Hi,
According to your description, my understanding is that the problem DC is configured with conditional forwarders to resolve names about other 2 trusted forests, and always times out. Besides, there is a delay or a time out the first few times when attempting
to resolve an external name.
Use NSlookup to confirm that if the conditional forwarder works. Open CMD on problem DC, type the command below and each line end with enter:
Nslookup
Server <IP address of the condition forwarder which used to resolve names on trust domain>
<name of the trust forest which you want to resolve>
If it works, try to increase time-out period:
Properties of Conditional Forwarders – Number of seconds before forward queries times out
– change the time.
If it doesn’t work, turn on exhaustive debugging mode. Open CMD on problem DC, type the command below and each line end with enter:
Nslookup
Set d2
Server <IP address of the condition forwarder which used to resolve names on trust domain>
<name of the trust forest which you want to resolve>
Post the result here.
Besides, for internet/external name resolving problem, we usually have another DNS server(except for DCs) which connected to Internet/external and used to resolve external/Internet names. And on DCs, configure forwarder and use forwarder to resolve external/Internet
names. If it is your case, check the forwarder setting on the problem DC, or use ping to test the network connectivity. Confirm that if the delay of name resolving caused by network delay.
Best Regards,
Eve Wang
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Are DNS requests intercepted?

Hi,
There's a site I'm trying to get to, but when I type in the address & go I always end up at a different site.
I've asked local friends whether they have the same problem & they don't.
I've flushed the dns cache on my pcs (I have the same problem no matter which one I use).
I've restarted the router (which supposedly clears the dns cache there).
I've tried using my phone to go the wireless route.
I always end up at the wrong address.
Thinking it might be an error in the BT DNS server's info I tried changing the dns servers on my PC to Google's and then OpenDNS.
I still end up at the wrong page.
What I'm wondering is whether changing the dns settings on my PCs actually has any effect.
Does BT intercept dns requests & route them through their own servers?
Many thanks.

pauliolio wrote:
Hi,
There's a site I'm trying to get to, but when I type in the address & go I always end up at a different site.
I've asked local friends whether they have the same problem & they don't.
I've flushed the dns cache on my pcs (I have the same problem no matter which one I use).
I've restarted the router (which supposedly clears the dns cache there).
I've tried using my phone to go the wireless route.
I always end up at the wrong address.
Thinking it might be an error in the BT DNS server's info I tried changing the dns servers on my PC to Google's and then OpenDNS.
I still end up at the wrong page.
What I'm wondering is whether changing the dns settings on my PCs actually has any effect.
Does BT intercept dns requests & route them through their own servers?
Many thanks.
Hi.
If, by altering the DNS server, you end up at the same place - this indicates it's a local issue.
Can you say what the website is ? If you don't wish it to be public, send me a private message with the website and I'll investigate.
http://www.andyweb.co.uk/shortcuts
http://www.andyweb.co.uk/pictures

WRT100 Router DNS Order (DHCP)

I have an issue with the WRT100 router which I had hoped would be fixed with a firmware update (currently v1.0.02). I asked Linksys to troubleshoot the issue and they passed it to software engineering at my request. Could you help me confirm that it is really a bug? If you have your DHCP server enabled in the router (most do) it will suggest DNS entries to the DHCP clients. But if you specify Static DNS entries in the router they sort to the bottom! This is just the opposite of what most routers do (including all the other Linksys models I've used). The DNS result are sorted... 1) ISP provided entires 2) ROUTER ip 3) STATIC entries If you as an administrator specify a static DNS (say for use with an active directory domain controller or to support OpenDNS use) the intention is that they be used first. For this to happen they must appear first on the list (provided by DHCP) .. not last! To work properly we need to reorder to the DNS entires... STATIC, ROUTER, ISP. Static (manual) entries should always proceed any automatically configured items. Do you have a WRT100? What order does your router sort the DNS entries? (You can check your DHCP client by running 'ipconfig/all' at a command prompt on most Microsoft OS.) Sample output: Default Gateway . . . . . . : 192.168.1.1 --Router DHCP Server . . . . . . . . : 192.168.1.1 --Router DNS Servers . . . . . . . . : 68.105.28.11 --ISP DNS1 68.105.29.11 --ISP DNS2 68.105.28.12 --ISP DNS3 192.168.1.1 --Router 208.67.222.222 --STATIC DNS 1 208.67.220.220 --STATIC DNS 2
Aland Coons

Try the Snow Leopard network forum area & do a search for your issue. There are quite a few threads like yours there - http://discussions.apple.com/forum.jspa?forumID=1343

SL constantly making DNS requests for "local" ?

I've been troubleshooting a problem with my DSL router crashing and noticed that my Macs continuously, even when idle, have nearly 200 open connections at any given time, whereas my Windows boxes peak at 50 and drop down to under 10 when idle. The Macs are running SL 10.6.2.
Poking around in the router logs, I found that the Macs are constantly making udp DNS requests to my router, even when I'm not browsing or doing anything else. tcpdump of udp and port 53 gives me the following:
00:21:53.371671 IP 192.168.0.8.59304 > 192.168.0.1.53: 18151+ SOA? local. (23)
00:21:53.674232 IP 192.168.0.8.49916 > 192.168.0.1.53: 48169+ SOA? local. (23)
00:21:53.977128 IP 192.168.0.8.52735 > 192.168.0.1.53: 25906+ SOA? local. (23)
00:21:54.279836 IP 192.168.0.8.60409 > 192.168.0.1.53: 18252+ SOA? local. (23)
00:21:54.582518 IP 192.168.0.8.52350 > 192.168.0.1.53: 61085+ SOA? local. (23)
00:21:54.885866 IP 192.168.0.8.62450 > 192.168.0.1.53: 21082+ SOA? local. (23)
00:21:55.189449 IP 192.168.0.8.56146 > 192.168.0.1.53: 32869+ SOA? local. (23)
00:21:55.494834 IP 192.168.0.8.50517 > 192.168.0.1.53: 19194+ SOA? local. (23)
00:21:55.797551 IP 192.168.0.8.52035 > 192.168.0.1.53: 7558+ SOA? local. (23)
00:21:56.100390 IP 192.168.0.8.52101 > 192.168.0.1.53: 40847+ SOA? local. (23)
00:21:56.403436 IP 192.168.0.8.52194 > 192.168.0.1.53: 6087+ SOA? local. (23)
00:21:56.706299 IP 192.168.0.8.52347 > 192.168.0.1.53: 9339+ SOA? local. (23)
00:21:57.009058 IP 192.168.0.8.56200 > 192.168.0.1.53: 25553+ SOA? local. (23)
00:21:57.312098 IP 192.168.0.8.51976 > 192.168.0.1.53: 20703+ SOA? local. (23)
00:21:57.616665 IP 192.168.0.8.54563 > 192.168.0.1.53: 54141+ SOA? local. (23)
00:21:57.923536 IP 192.168.0.8.65097 > 192.168.0.1.53: 45734+ SOA? local. (23)
00:21:58.226243 IP 192.168.0.8.54125 > 192.168.0.1.53: 33647+ SOA? local. (23)
00:21:58.529128 IP 192.168.0.8.54571 > 192.168.0.1.53: 17218+ SOA? local. (23)
00:21:58.831897 IP 192.168.0.8.60218 > 192.168.0.1.53: 48469+ SOA? local. (23)
00:21:59.135020 IP 192.168.0.8.60466 > 192.168.0.1.53: 37003+ SOA? local. (23)
00:21:59.437998 IP 192.168.0.8.58798 > 192.168.0.1.53: 17670+ SOA? local. (23)
00:21:59.741022 IP 192.168.0.8.60276 > 192.168.0.1.53: 47469+ SOA? local. (23)
00:22:00.055207 IP 192.168.0.8.57066 > 192.168.0.1.53: 20384+ SOA? local. (23)
00:22:00.360458 IP 192.168.0.8.50152 > 192.168.0.1.53: 29721+ SOA? local. (23)
00:22:00.663357 IP 192.168.0.8.63487 > 192.168.0.1.53: 35833+ SOA? local. (23)
00:22:00.966073 IP 192.168.0.8.64900 > 192.168.0.1.53: 34951+ SOA? local. (23)
00:22:01.271649 IP 192.168.0.8.64314 > 192.168.0.1.53: 25719+ SOA? local. (23)
00:22:01.574530 IP 192.168.0.8.55922 > 192.168.0.1.53: 5842+ SOA? local. (23)
00:22:01.877146 IP 192.168.0.8.51874 > 192.168.0.1.53: 59071+ SOA? local. (23)
00:22:02.179921 IP 192.168.0.8.56913 > 192.168.0.1.53: 43487+ SOA? local. (23)
00:22:02.482738 IP 192.168.0.8.62907 > 192.168.0.1.53: 26628+ SOA? local. (23)
00:22:02.785409 IP 192.168.0.8.51599 > 192.168.0.1.53: 57463+ SOA? local. (23)
00:22:03.088321 IP 192.168.0.8.60417 > 192.168.0.1.53: 8857+ SOA? local. (23)
00:22:03.391227 IP 192.168.0.8.57872 > 192.168.0.1.53: 36002+ SOA? local. (23)
00:22:03.694211 IP 192.168.0.8.58774 > 192.168.0.1.53: 1662+ SOA? local. (23)
192.168.0.8 is my Mac and 192.168.0.1 is my DSL router. The Mac is ip'd using DHCP on the router. The router sends DNS requests from my clients out to my ISPs DNS servers.
Eventually, the DNS requests timeout and I get this:
00:21:43.145103 IP 205.171.3.65.53 > 192.168.0.8.52959: 38258 NXDomain 0/1/0 (98)
00:21:43.450086 IP 205.171.3.65.53 > 192.168.0.8.55938: 46832 NXDomain 0/1/0 (98)
00:21:43.763304 IP 205.171.3.65.53 > 192.168.0.8.50265: 62399 NXDomain 0/1/0 (98)
00:21:44.049705 IP 205.171.3.65.53 > 192.168.0.8.59991: 5960 NXDomain 0/1/0 (98)
It's a never-ending cycle that eventually kills my router.
If I'm reading the tcpdump output correctly, SL appears to be looking for some server named "local" 3 times every second. The TTL is roughly 90 seconds, so 3 requests/second gets me to an average of 180 connections at any give time -- which is approximately what my router is showing. If I do start browsing the connection count goes even higher. Trying to use both Macs at the same time has caused my router to crash due to running out of memory (it's obviously a very weak router .
Can someone give me some insight into what SL is doing and how I can stop this?
Thanks,
Randy

Does this server handle DNS requests?
If so, make sure under the local static IP for DNS servers you can try 127.0.0.1, and server IP.
Under the DNS tab make sure you have the ISP IP's under forwarder.
As a safety open terminal and run
su changeip -checkhostname

Cbac and dns requests

can anyone tell me why my dns requests on cbac are not working, I allowed everything from inside out, but dns requests are not allowed for some reasons...
Building configuration...
Current configuration : 3265 bytes
! Last configuration change at 08:47:57 UTC Thu Jun 14 2012 by admin
version 15.1
no service pad
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug datetime msec localtime
service timestamps log datetime msec localtime
service password-encryption
hostname oecl
boot-start-marker
boot-end-marker
logging buffered 64000
enable secret 5 $1$kIPV$0ixUVG.EY10hIznM/HN5z/
aaa new-model
aaa authentication login default local-case
aaa session-id common
no ipv6 source-route
no ipv6 cef
no ip source-route
ip cef
ip dhcp excluded-address 10.28.3.1 10.28.3.2
ip dhcp excluded-address 10.28.4.1 10.28.4.2
ip dhcp pool OEC2al
network 10.28.3.0 255.255.255.0
default-router 10.28.3.1
dns-server 10.28.3.1
domain-name oec2al.co.uk
lease 5
ip dhcp pool Wellmax
network 10.28.4.0 255.255.255.0
default-router 10.28.4.1
dns-server 10.28.4.1
lease 5
no ip bootp server
ip name-server 8.8.8.8
ip name-server 4.2.2.5
ip inspect name firewall tcp
ip inspect name firewall udp
ip inspect name firewall icmp
multilink bundle-name authenticated
crypto pki token default removal timeout 0
license udi pid CISCO2911/K9 sn FCZ1605705Q
username admin secret 5 $1$L94s$LrPxn0IWRRu74KEQvlWIL/
redundancy
ip tcp selective-ack
ip tcp timestamp
ip tcp path-mtu-discovery
interface Loopback1
ip address 1.1.1.1 255.255.255.0
interface Embedded-Service-Engine0/0
no ip address
shutdown
interface GigabitEthernet0/0
description WAN
ip address 10.28.9.241 255.255.255.0
ip access-group 102 in
ip nat outside
ip inspect firewall out
ip virtual-reassembly in
duplex auto
speed auto
interface GigabitEthernet0/1
no ip address
ip nat inside
ip virtual-reassembly in
duplex auto
speed auto
interface GigabitEthernet0/1.1
encapsulation dot1Q 1 native
no cdp enable
interface GigabitEthernet0/1.3
encapsulation dot1Q 3
ip address 10.28.3.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
no cdp enable
interface GigabitEthernet0/1.4
encapsulation dot1Q 4
ip address 10.28.4.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
no cdp enable
interface GigabitEthernet0/2
no ip address
shutdown
duplex auto
speed auto
ip forward-protocol nd
no ip http server
no ip http secure-server
ip dns server
ip nat inside source list 100 interface GigabitEthernet0/0 overload
ip route 0.0.0.0 0.0.0.0 10.28.9.251
access-list 5 remark -=VTY local access=-
access-list 5 permit 10.28.3.0 0.0.0.255
access-list 100 remark -=NAT access=-
access-list 100 permit ip 10.28.0.0 0.0.255.255 any
access-list 101 remark -=VTY access restriction=-
access-list 101 permit ip host 181.143.217.54 any
access-list 102 remark -=Local firewall=-
access-list 102 permit icmp any any unreachable
access-list 102 permit icmp any any time-exceeded
access-list 102 permit icmp any any echo-reply
access-list 102 permit ip host 181.143.217.54 any
no cdp run
control-plane
line con 0
line aux 0
line 2
no activation-character
no exec
transport preferred none
transport input all
transport output pad telnet rlogin lapb-ta mop udptn v120 ssh
stopbits 1
line vty 0 4
access-class 5 in
transport input ssh
scheduler allocate 20000 1000
end

I have set up two public dns servers, it works ok until i enable access-list 102, i solved this problem by adding to acl 102 entry permit tcp any eq 53 any, but on different router (also 2911) everything was ok and cbac and same config were similar. What could be wrong?

Config content router dns record

Does anyone know how to config the DNS record on the content router

The FQDN mapping on the Content Router (CR) is received from the CDM based on the configuration of the Websites in the CDM. When you are configuring a website on the CDM, populating the 'Request Routed FQDN' field will cause the CDM to inform the CR that it should start responding to DNS requests for that domain.
In short, there is nothing that needs to be configured directly on the CR -- all of the configuration happens on the CDM.
~Zach

Redirect all DNS requests for a certain domain to a specific DNS Server

Hello,
I have setup a home lab to do some Microsoft training on. My lab domain name is "demo.lab". What I want to do is configure my cisco router to forward any dns requests to demo.lab to my Active Directory Server.
For example
If I ping mail.demo.lab, I want that reqest to be forwarded to my lab domain controller (dc01.demo.lab).
I have configured a SOA record on the Cisco router like so, but it still does not foward the reqest on (10.10.10.10 is the IP address of dc01.demo.lab).
ip dns primary demo.lab soa 10.10.10.10 postmaster.demo.lab
Any clues as to what i'm missing?
Thanks
Peter

Hi Karsten,
Yep my computer had the router as its primary DNS Server. The config you supplied worked! Thanks very much :)
Hi Cisco Freak,
Yep my AD server was also a DNS server. Yes that was one option, but I just didn't want to keep changing my DNS as my laptop goes to/from work with me. The config that Karsten supplied worked though.
Hi Terry,
Thanks for the link. I believe I had configured it correctly as per that docuemnt, but it didn't work for some reason. Still go reference material though.
The other option would have been to configure the router to use my AD server as its primary name server host like so;
ip name-server 10.10.10.10
ip name-server 8.8.8.8
The only problem would be that if/when my DC is offline, there would be a small delay when doing DNS requests, and since my internet is shared with my house mate, I didn't want to disrupt her too much.
Thanks again for your help!
Cheers
Peter

GRC 10.1 - Routing at Request Submission in case of SOD violations

I am trying to configure MSMP workflow or risks analysis while creating userid
1. No Risks >> User created and access assigned automatically
2. Risks found >> forward to security team to review and approve
I have checked the standard functional module - GRAC_MSMP_DETOUR_SODVIOL cannot be used in AC 10.0 . This is only be used as Routing Rule after first stage approval and at subsequent stages as per Note - 1783157 - Routing at Request Submission in case of SOD violations
Can anyone advise the standard SAP delivered rule / functional module we can use in GRC AC 10.1 to achieve the outcome at the time of request submission ??

Hi Anil,
You have enable riak analysis at submission buy setting parameter and the need to have a first stage as dummy where risk analysis result can be analysed and have a detour at this dummy stage so that in case of risk request is forwarded to next stage.
Hope that helps..
Regards
Ashish

DNS request timed out. timeout was 2 seconds

Hi
Why it is saying DNS request timed out was 2 seconds and showing the IPs under non-authoritative answers?
This is member DC windows 2008 R2. Primary DNS is set as 127.0.0.1 and secondary DNS is set to 192.168.10.6 which is main DC.
C:\Users\admin>nslookup filter-servers.mailguard.com.au
Server: localhost
Address: 127.0.0.1
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
Non-authoritative answer:
Name:    filter-servers.mailguard.com.au
Addresses:50.23.252.165
199.193.116.73.. more

HI
Use ISP DNS servers and forward DNS query from internal DNS to ISP DNS servers,

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

Route the request from Proxy Service in OSB to external BusinessService URL

Hi,
How to route the request from Proxy service to the Business Service(Which is not registered in the OSB) using End point URL.Dynamically look up the URL and route the req from Proxy to Business service.
thanks in Advance
Edited by: user10680427 on Jul 14, 2009 2:57 AM
Edited by: user10680427 on Jul 14, 2009 3:34 AM

Hi..
Just set in within a routing options in a route node, either dynamic routing or just setting the uri, depends on your specific case..

Adding routes not on the Global Zone

Is it possible to add a route to a non global zone? if not, is there a way to manipulate the route coming from non global zone?

I don't think so. There's only one kernel and only one routing table. There might be some workarounds though.
Can you describe a little more of what you're trying to do? It might be possible to think up some workarounds. For instance, ipnat might be able to do useful rewrites.
Darren

Nslookup: DNS request timed out. time out was 2 seconds. (When the primary DNS is down)

Hi All,
I have set up 2 Windows Server 2012 domain controllers (DCA & DCB). DCA points at DCB as the primary DNS, and itself as the alternate DNS. DCB points at DCA as the primary DNS, and itself as the alternate DNS.
When both DCs are running and if I do an nslookup on DCA: The result is as follows:
Default Server: dcb.testdomain.com
Address: 30.30.30.2
nslookup on DCB:
Default Server: dca.testdomain.com
Address: 30.30.30.1
Client PC (Windows 7 Pro):
1st DNS : 30.30.30.31
Alternate DNS: 30.30.30.32
nslookup on the client PC
Default Server: dca.testdomain.com
Address: 30.30.30.1
Up to here everything is fine. Now if I turn off DCA, and do an nslookup, the result is as follows:
DCB nslookup:
DNS request timed out.
time out was 2 seconds.
Default Server Unknown
Address: 30.30.30.31
Client PC nslookup:
DNS request timed out.
time out was 2 seconds.
Default Server Unknown
Address: 30.30.30.31
I waited for more than 15 minutes an tried again, it didn't help.
I have been reading a few similar posts on this matter, but couldn't find the answer.
I would expected it to display the DCB when I do an nslookup.
Question 1: Shouldn't that display DCB rather than displaying a time out message when I do nslookup?
Question 2: The fact that it displays a time out message, does it mean that more configuration needs to be done? If so please kindly advice what needs to be done.
I did an ipconfig /displaydns command. I realized that the order of DNS have changed on both DCB and the Client PC:
Now, they both display DCB on the top of the list, whereas they were displaying DCA on the top of the list prior to the shut down.
Question 3: Does it mean that the Client PC now knows that the 1st DNS is down and so it's using the 2nd DNS?
If so, why does the nslookup display the time out message?
Question 4: Is it possible to configure either of DNS Server or the DNS client, so it displays the 2nd DNS when the first DNS is not accessible and when I do nslookup?
Thank you for.

Hi Ton_2013,
Based on my understanding, the issue we are experiencing is that: when the primary DNS server is down, the result of the tool Nslookup is to diaplay the time out message at first. Right?
Based on my knowledge, timed out message is means that the server did not respond to a request after a certain amount of time and a certain number of retries. Because the primary DNS server is down, it can't respond to this request and time is out. When
the primary DNS server can't respond, the secondary DNS server works to ensure effective work. And the order is changed as you said.
As to the reason why the result is still the same even when the order has changed, we can try to use Network Monitor to capture network traffic and view and analyze it to find the cause. And the cause may be the cache. For your information, please refer
to the following link to download the tool Network Monitor:
http://www.microsoft.com/en-hk/download/details.aspx?id=4865
Regards,
Lany Zhang

Routing DNS requests in a zone to a default host

Similar Messages

Maybe you are looking for