Group:  English: Windows Server ยป microsoft.public.windows.server.dns
Thread: recursive query fails

DotNetBag
.NET Development Newsgroups

HTVi
TV Discussion Newsgroups

Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
Rising Antivirus 2006

recursive query fails
Freddie 05.06.2007 21:38:01
windows 2003 everything has been working ok.
then client calls and says no internet on her PC
I go onsite and I can't get internet started , I tried to pinged the
www.yahoo.com or even the ISP's DNS and it fails,
No error messages in DNS event,
but when I try to do a recursive query it fails,

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator.SERVER>nslookup
Default Server: xyanttech.local
Address: 192.168.100.2

[Quoted Text]
> exit

C:\Documents and Settings\Administrator.SERVER>ping www.yahoo.com
Ping request could not find host www.yahoo.com. Please check the name and
try ag
ain.

C:\Documents and Settings\Administrator.SERVER>
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator.SERVER>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : server
Primary Dns Suffix . . . . . . . : XYANTTech.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : XYANTTech.local

Ethernet adapter Local:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 S Server Adapter #2
Physical Address. . . . . . . . . : 00-0E-0C-A9-FE-E1
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.100.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.100.1
DNS Servers . . . . . . . . . . . : 192.168.100.2

C:\Documents and Settings\Administrator.SERVER>
any help ?

Thanks again.
Freddie
Re: recursive query fails
"Kevin D. Goodknecht Sr. [MVP]" <admin[ at ]nospam.WFTX.US> 06.06.2007 11:30:42


In news:B011AF5D-D8D2-4989-B2E4-4C825E081968[ at ]microsoft.com,
Freddie <Freddie[ at ]discussions.microsoft.com> typed:
[Quoted Text]
> windows 2003 everything has been working ok.
> then client calls and says no internet on her PC
> I go onsite and I can't get internet started , I tried to pinged the
> www.yahoo.com or even the ISP's DNS and it fails,
> No error messages in DNS event,
> but when I try to do a recursive query it fails,
>
> Microsoft Windows [Version 5.2.3790]
> (C) Copyright 1985-2003 Microsoft Corp.
>
> C:\Documents and Settings\Administrator.SERVER>nslookup
> Default Server: xyanttech.local
> Address: 192.168.100.2
>
>> exit
>
> C:\Documents and Settings\Administrator.SERVER>ping www.yahoo.com
> Ping request could not find host www.yahoo.com. Please check the name
> and try ag
> ain.
>
> C:\Documents and Settings\Administrator.SERVER>
> Microsoft Windows [Version 5.2.3790]
> (C) Copyright 1985-2003 Microsoft Corp.
>
> C:\Documents and Settings\Administrator.SERVER>ipconfig /all
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : server
> Primary Dns Suffix . . . . . . . : XYANTTech.local
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : Yes
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : XYANTTech.local
>
> Ethernet adapter Local:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel(R) PRO/100 S Server
> Adapter #2 Physical Address. . . . . . . . . : 00-0E-0C-A9-FE-E1
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.100.2
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.100.1
> DNS Servers . . . . . . . . . . . : 192.168.100.2
>
> C:\Documents and Settings\Administrator.SERVER>
> any help ?

Have you configured a forwarder for your DNS server?
Are the Root Hints resolved to IP addresses on the Root Hints tab?



--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps

===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================


Re: recursive query fails
Freddie 07.06.2007 22:33:00
I belive everything was working ok.
how to check on this?



"Kevin D. Goodknecht Sr. [MVP]" wrote:

[Quoted Text]
>
>
> In news:B011AF5D-D8D2-4989-B2E4-4C825E081968[ at ]microsoft.com,
> Freddie <Freddie[ at ]discussions.microsoft.com> typed:
> > windows 2003 everything has been working ok.
> > then client calls and says no internet on her PC
> > I go onsite and I can't get internet started , I tried to pinged the
> > www.yahoo.com or even the ISP's DNS and it fails,
> > No error messages in DNS event,
> > but when I try to do a recursive query it fails,
> >
> > Microsoft Windows [Version 5.2.3790]
> > (C) Copyright 1985-2003 Microsoft Corp.
> >
> > C:\Documents and Settings\Administrator.SERVER>nslookup
> > Default Server: xyanttech.local
> > Address: 192.168.100.2
> >
> >> exit
> >
> > C:\Documents and Settings\Administrator.SERVER>ping www.yahoo.com
> > Ping request could not find host www.yahoo.com. Please check the name
> > and try ag
> > ain.
> >
> > C:\Documents and Settings\Administrator.SERVER>
> > Microsoft Windows [Version 5.2.3790]
> > (C) Copyright 1985-2003 Microsoft Corp.
> >
> > C:\Documents and Settings\Administrator.SERVER>ipconfig /all
> >
> > Windows IP Configuration
> >
> > Host Name . . . . . . . . . . . . : server
> > Primary Dns Suffix . . . . . . . : XYANTTech.local
> > Node Type . . . . . . . . . . . . : Unknown
> > IP Routing Enabled. . . . . . . . : Yes
> > WINS Proxy Enabled. . . . . . . . : No
> > DNS Suffix Search List. . . . . . : XYANTTech.local
> >
> > Ethernet adapter Local:
> >
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : Intel(R) PRO/100 S Server
> > Adapter #2 Physical Address. . . . . . . . . : 00-0E-0C-A9-FE-E1
> > DHCP Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 192.168.100.2
> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > Default Gateway . . . . . . . . . : 192.168.100.1
> > DNS Servers . . . . . . . . . . . : 192.168.100.2
> >
> > C:\Documents and Settings\Administrator.SERVER>
> > any help ?
>
> Have you configured a forwarder for your DNS server?
> Are the Root Hints resolved to IP addresses on the Root Hints tab?
>
>
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This Helps
>
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
> http://www.lonestaramerica.com/
> http://support.wftx.us/
> http://message.wftx.us/
> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
> http://www.oehelp.com/OEBackup/Default.aspx
> ===================================
>
>
>
Re: recursive query fails
"Kevin D. Goodknecht Sr. [MVP]" <admin[ at ]nospam.WFTX.US> 08.06.2007 03:25:59
Read inline please.

In news:1E5BFAB5-E529-44B2-BD5E-7778DFCCEAA1[ at ]microsoft.com,
Freddie <Freddie[ at ]discussions.microsoft.com> typed:
[Quoted Text]
> I belive everything was working ok.
> how to check on this?

Use the DNS Management Console, to connect to this DNS server, if not
already connected. Right click on the server object in the console, choose
properties, select the Forwarrders tab, select "All other DNS domains" and
enter the IP address of your router, if it supports DNS Proxying, if it does
not support DNS proxying, enter the IP of your ISP's DNS server.
Select the Root Hints tab, if they are not resolved, remove them and click
the copy from server button and enter 198.41.0.4 (ICANN Root Server SOA
master).

If the Forwarders tab and Root Hints tab are both unavailable because it is
a Root Server, expand forward lookup zones, right click on the zone named
with a dot ".", and delete it. Close and reopen the console which should
load the root hints and make the Forwarders tab available.



--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps

===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================


Re: recursive query fails
Freddie 08.06.2007 19:54:03
I see the server and dns forwarder points to ISP DNS
when I try to connect to 198.41.0.4 connection times out
rememeber I can not ping the ISP 's DNS
does not resolves any outside IP or Name
thanks
freddie


"Kevin D. Goodknecht Sr. [MVP]" wrote:

[Quoted Text]
> Read inline please.
>
> In news:1E5BFAB5-E529-44B2-BD5E-7778DFCCEAA1[ at ]microsoft.com,
> Freddie <Freddie[ at ]discussions.microsoft.com> typed:
> > I belive everything was working ok.
> > how to check on this?
>
> Use the DNS Management Console, to connect to this DNS server, if not
> already connected. Right click on the server object in the console, choose
> properties, select the Forwarrders tab, select "All other DNS domains" and
> enter the IP address of your router, if it supports DNS Proxying, if it does
> not support DNS proxying, enter the IP of your ISP's DNS server.
> Select the Root Hints tab, if they are not resolved, remove them and click
> the copy from server button and enter 198.41.0.4 (ICANN Root Server SOA
> master).
>
> If the Forwarders tab and Root Hints tab are both unavailable because it is
> a Root Server, expand forward lookup zones, right click on the zone named
> with a dot ".", and delete it. Close and reopen the console which should
> load the root hints and make the Forwarders tab available.
>
>
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This Helps
>
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
> http://www.lonestaramerica.com/
> http://support.wftx.us/
> http://message.wftx.us/
> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
> http://www.oehelp.com/OEBackup/Default.aspx
> ===================================
>
>
>
Re: recursive query fails
"Kevin D. Goodknecht Sr. [MVP]" <admin[ at ]nospam.WFTX.US> 08.06.2007 20:34:58
Read inline please.

In news:A98D4598-2F43-48C4-BAEA-3CD7EE37BE55[ at ]microsoft.com,
Freddie <Freddie[ at ]discussions.microsoft.com> typed:
[Quoted Text]
> I see the server and dns forwarder points to ISP DNS
> when I try to connect to 198.41.0.4 connection times out
> rememeber I can not ping the ISP 's DNS
Ping is not the tool for testing this, use the portqry tool to see if 53
UDP/TCP can be opened.

> does not resolves any outside IP or Name

Check your Firewall to make sure you can connect to port 53 UDP/TCP at any
IP address on the internet from any internal IP/port combination.

Like this
from <InternalDNSIP> any port
to any Ipaddress port 53 UDP/TCP




--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps

===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================


Re: recursive query fails
Freddie 12.06.2007 19:55:00
is this what you are talking about?
this is from command promt of the Server (domain controler and DNS)

C:\Company\Support\portqry>portqry -n server

Querying target system called:

server

Attempting to resolve name to IP address...


Name resolved to 192.168.100.2

querying...

TCP port 80 (http service): LISTENING

C:\Company\Support\portqry>portqry -n local

Querying target system called:

local

Attempting to resolve name to IP address...

Failed to resolve name to IP address

C:\Company\Support\portqry>portqry -n 192.168.100.2

Querying target system called:

192.168.100.2

Attempting to resolve IP address to a name...


IP address resolved to server.XYANTTech.local

querying...

TCP port 80 (http service): LISTENING

C:\Company\Support\portqry>portqry -wport 53

PortQry Version 2.0
Watching port: 53

Checking for changes every 60 seconds

**press escape to stop watching port

============
System Date: Tue Jun 12 14:48:13 2007


Service Name: DNS
Display Name: DNS Server
Service Type: runs in its own process

PID Port Local IP State Remote IP:Port
1732 TCP 53 0.0.0.0 LISTENING 0.0.0.0:51331
1732 TCP 1040 0.0.0.0 LISTENING 0.0.0.0:26630
1732 TCP 2215 127.0.0.1 ESTABLISHED 127.0.0.1:389
1732 UDP 1033 0.0.0.0 *:*
1732 UDP 53 127.0.0.1 *:*
1732 UDP 1032 127.0.0.1 *:*
1732 UDP 1034 127.0.0.1 *:*
1732 UDP 53 192.168.100.2 *:*

Port Statistics

TCP mappings: 3
UDP mappings: 5

TCP ports in a LISTENING state: 2 = 66.67%
TCP ports in a ESTABLISHED state: 1 = 33.33%



escape key pressed: stopped watching port 53
System Date: Tue Jun 12 14:48:58 2007


C:\Company\Support\portqry>portqry -wport 53

PortQry Version 2.0
Watching port: 53

Checking for changes every 60 seconds

**press escape to stop watching port

============
System Date: Tue Jun 12 14:49:07 2007


Service Name: DNS
Display Name: DNS Server
Service Type: runs in its own process

PID Port Local IP State Remote IP:Port
1732 TCP 53 0.0.0.0 LISTENING 0.0.0.0:51331
1732 TCP 1040 0.0.0.0 LISTENING 0.0.0.0:26630
1732 TCP 2215 127.0.0.1 ESTABLISHED 127.0.0.1:389
1732 UDP 1033 0.0.0.0 *:*
1732 UDP 53 127.0.0.1 *:*
1732 UDP 1032 127.0.0.1 *:*
1732 UDP 1034 127.0.0.1 *:*
1732 UDP 53 192.168.100.2 *:*

Port Statistics

TCP mappings: 3
UDP mappings: 5

TCP ports in a LISTENING state: 2 = 66.67%
TCP ports in a ESTABLISHED state: 1 = 33.33%



escape key pressed: stopped watching port 53
System Date: Tue Jun 12 14:49:38 2007

Thanks again
Freddie

"Kevin D. Goodknecht Sr. [MVP]" wrote:

[Quoted Text]
> Read inline please.
>
> In news:A98D4598-2F43-48C4-BAEA-3CD7EE37BE55[ at ]microsoft.com,
> Freddie <Freddie[ at ]discussions.microsoft.com> typed:
> > I see the server and dns forwarder points to ISP DNS
> > when I try to connect to 198.41.0.4 connection times out
> > rememeber I can not ping the ISP 's DNS
> Ping is not the tool for testing this, use the portqry tool to see if 53
> UDP/TCP can be opened.
>
> > does not resolves any outside IP or Name
>
> Check your Firewall to make sure you can connect to port 53 UDP/TCP at any
> IP address on the internet from any internal IP/port combination.
>
> Like this
> from <InternalDNSIP> any port
> to any Ipaddress port 53 UDP/TCP
>
>
>
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This Helps
>
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
> http://www.lonestaramerica.com/
> http://support.wftx.us/
> http://message.wftx.us/
> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
> http://www.oehelp.com/OEBackup/Default.aspx
> ===================================
>
>
>
Re: recursive query fails
Freddie 12.06.2007 20:06:01

or this is what you are talking about?


[Quoted Text]
> q

resolving service name using local services file...
UDP port resolved to the 'domain' service

IP address resolved to server.XYANTTech.local

querying...

UDP port 53 (domain service): LISTENING

> exit

exiting PortQry Interactive Mode...



C:\Company\Support\portqry>portqry -n 192.168.100.2 -e 53 -p UDP -i

PortQry Interactive Mode

Type 'help' for a list of commands

Default Node: 192.168.100.2

Current option values:
end port= 53
protocol= UDP
source port= 0 (ephemeral)
> q

resolving service name using local services file...
UDP port resolved to the 'domain' service

IP address resolved to server.XYANTTech.local

querying...

UDP port 53 (domain service): LISTENING or FILTERED

Sending DNS query to UDP port 53...

DNS query timed out

> q

resolving service name using local services file...
UDP port resolved to the 'domain' service

IP address resolved to server.XYANTTech.local

querying...

UDP port 53 (domain service): LISTENING

> q

resolving service name using local services file...
UDP port resolved to the 'domain' service

IP address resolved to server.XYANTTech.local

querying...

UDP port 53 (domain service): LISTENING or FILTERED

Sending DNS query to UDP port 53...

DNS query timed out

Thanks
Again
Freddie

"Kevin D. Goodknecht Sr. [MVP]" wrote:

> Read inline please.
>
> In news:A98D4598-2F43-48C4-BAEA-3CD7EE37BE55[ at ]microsoft.com,
> Freddie <Freddie[ at ]discussions.microsoft.com> typed:
> > I see the server and dns forwarder points to ISP DNS
> > when I try to connect to 198.41.0.4 connection times out
> > rememeber I can not ping the ISP 's DNS
> Ping is not the tool for testing this, use the portqry tool to see if 53
> UDP/TCP can be opened.
>
> > does not resolves any outside IP or Name
>
> Check your Firewall to make sure you can connect to port 53 UDP/TCP at any
> IP address on the internet from any internal IP/port combination.
>
> Like this
> from <InternalDNSIP> any port
> to any Ipaddress port 53 UDP/TCP
>
>
>
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This Helps
>
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
> http://www.lonestaramerica.com/
> http://support.wftx.us/
> http://message.wftx.us/
> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
> http://www.oehelp.com/OEBackup/Default.aspx
> ===================================
>
>
>
Re: recursive query fails
"Kevin D. Goodknecht Sr. [MVP]" <admin[ at ]nospam.WFTX.US> 13.06.2007 11:56:02
Read inline please.

In news:37F105F9-C58F-43E4-AA52-8D09CF6305FA[ at ]microsoft.com,
Freddie <Freddie[ at ]discussions.microsoft.com> typed:
[Quoted Text]
> or this is what you are talking about?
>
>
>> q
>
> resolving service name using local services file...
> UDP port resolved to the 'domain' service
>
> IP address resolved to server.XYANTTech.local
>
> querying...
>
> UDP port 53 (domain service): LISTENING
>
>> exit
>
> exiting PortQry Interactive Mode...
>
>
>
> C:\Company\Support\portqry>portqry -n 192.168.100.2 -e 53 -p UDP -i
>
> PortQry Interactive Mode
>
> Type 'help' for a list of commands
>
> Default Node: 192.168.100.2
>
> Current option values:
> end port= 53
> protocol= UDP
> source port= 0 (ephemeral)
>> q
>
> resolving service name using local services file...
> UDP port resolved to the 'domain' service
>
> IP address resolved to server.XYANTTech.local
>
> querying...
>
> UDP port 53 (domain service): LISTENING or FILTERED
>
> Sending DNS query to UDP port 53...
>
> DNS query timed out
>
>> q
>
> resolving service name using local services file...
> UDP port resolved to the 'domain' service
>
> IP address resolved to server.XYANTTech.local
>
> querying...
>
> UDP port 53 (domain service): LISTENING
>
>> q
>
> resolving service name using local services file...
> UDP port resolved to the 'domain' service
>
> IP address resolved to server.XYANTTech.local
>
> querying...
>
> UDP port 53 (domain service): LISTENING or FILTERED
>
> Sending DNS query to UDP port 53...
>
> DNS query timed out

It certainly looks like something is blocking DNS ports.

Use this command from the Server with DNS:
portqry -n 198.41.0.4 -e 53 -p BOTH

This is the response you should get:
Querying target system called:

198.41.0.4

Attempting to resolve IP address to a name...


IP address resolved to a.root-servers.net

querying...

TCP port 53 (domain service): LISTENING

UDP port 53 (domain service): LISTENING


--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps

===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================


Re: recursive query fails
Freddie 19.06.2007 18:26:06
this is what I am getting with your command
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator.SERVER>cd C:\Company\Support\portqry

C:\Company\Support\portqry>portqry -n 198.41.0.4 -e 53 -p BOTH

Querying target system called:

198.41.0.4

Attempting to resolve IP address to a name...

Failed to resolve IP address to name

querying...

TCP port 53 (domain service): FILTERED

UDP port 53 (domain service): LISTENING or FILTERED

Sending DNS query to UDP port 53...

DNS query timed out

C:\Company\Support\portqry>portqry -n 198.192.100.2 -e 53 -p BOTH

Querying target system called:

198.192.100.2

Attempting to resolve IP address to a name...

Failed to resolve IP address to name

querying...

TCP port 53 (domain service): FILTERED

UDP port 53 (domain service): LISTENING or FILTERED

Sending DNS query to UDP port 53...

DNS query timed out

C:\Company\Support\portqry>portqry -n 151.164.23.201 -e 53 -p BOTH

Querying target system called:

151.164.23.201

Attempting to resolve IP address to a name...

Failed to resolve IP address to name

querying...

TCP port 53 (domain service): FILTERED

UDP port 53 (domain service): LISTENING or FILTERED

Sending DNS query to UDP port 53...

DNS query timed out

C:\Company\Support\portqry>

any hope for me.
Freddie

"Kevin D. Goodknecht Sr. [MVP]" wrote:

[Quoted Text]
> Read inline please.
>
> In news:37F105F9-C58F-43E4-AA52-8D09CF6305FA[ at ]microsoft.com,
> Freddie <Freddie[ at ]discussions.microsoft.com> typed:
> > or this is what you are talking about?
> >
> >
> >> q
> >
> > resolving service name using local services file...
> > UDP port resolved to the 'domain' service
> >
> > IP address resolved to server.XYANTTech.local
> >
> > querying...
> >
> > UDP port 53 (domain service): LISTENING
> >
> >> exit
> >
> > exiting PortQry Interactive Mode...
> >
> >
> >
> > C:\Company\Support\portqry>portqry -n 192.168.100.2 -e 53 -p UDP -i
> >
> > PortQry Interactive Mode
> >
> > Type 'help' for a list of commands
> >
> > Default Node: 192.168.100.2
> >
> > Current option values:
> > end port= 53
> > protocol= UDP
> > source port= 0 (ephemeral)
> >> q
> >
> > resolving service name using local services file...
> > UDP port resolved to the 'domain' service
> >
> > IP address resolved to server.XYANTTech.local
> >
> > querying...
> >
> > UDP port 53 (domain service): LISTENING or FILTERED
> >
> > Sending DNS query to UDP port 53...
> >
> > DNS query timed out
> >
> >> q
> >
> > resolving service name using local services file...
> > UDP port resolved to the 'domain' service
> >
> > IP address resolved to server.XYANTTech.local
> >
> > querying...
> >
> > UDP port 53 (domain service): LISTENING
> >
> >> q
> >
> > resolving service name using local services file...
> > UDP port resolved to the 'domain' service
> >
> > IP address resolved to server.XYANTTech.local
> >
> > querying...
> >
> > UDP port 53 (domain service): LISTENING or FILTERED
> >
> > Sending DNS query to UDP port 53...
> >
> > DNS query timed out
>
> It certainly looks like something is blocking DNS ports.
>
> Use this command from the Server with DNS:
> portqry -n 198.41.0.4 -e 53 -p BOTH
>
> This is the response you should get:
> Querying target system called:
>
> 198.41.0.4
>
> Attempting to resolve IP address to a name...
>
>
> IP address resolved to a.root-servers.net
>
> querying...
>
> TCP port 53 (domain service): LISTENING
>
> UDP port 53 (domain service): LISTENING
>
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This Helps
>
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
> http://www.lonestaramerica.com/
> http://support.wftx.us/
> http://message.wftx.us/
> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
> http://www.oehelp.com/OEBackup/Default.aspx
> ===================================
>
>
>
Re: recursive query fails
"Kevin D. Goodknecht Sr. [MVP]" <admin[ at ]nospam.WFTX.US> 20.06.2007 20:48:51
Read inline please.

In news:384AB127-B452-4B00-B3F3-D44FF6C26AF4[ at ]microsoft.com,
Freddie <Freddie[ at ]discussions.microsoft.com> typed:
[Quoted Text]
> this is what I am getting with your command
> Microsoft Windows [Version 5.2.3790]
> (C) Copyright 1985-2003 Microsoft Corp.
>
> C:\Documents and Settings\Administrator.SERVER>cd
> C:\Company\Support\portqry
>
> C:\Company\Support\portqry>portqry -n 198.41.0.4 -e 53 -p BOTH
>
> Querying target system called:
>
> 198.41.0.4
>
> Attempting to resolve IP address to a name...
>
> Failed to resolve IP address to name
>
> querying...
>
> TCP port 53 (domain service): FILTERED
>
> UDP port 53 (domain service): LISTENING or FILTERED
>
> Sending DNS query to UDP port 53...
>
> DNS query timed out
>
> C:\Company\Support\portqry>portqry -n 198.192.100.2 -e 53 -p BOTH
>
> Querying target system called:
>
> 198.192.100.2
>
> Attempting to resolve IP address to a name...
>
> Failed to resolve IP address to name
>
> querying...
>
> TCP port 53 (domain service): FILTERED
>
> UDP port 53 (domain service): LISTENING or FILTERED
>
> Sending DNS query to UDP port 53...
>
> DNS query timed out
>
> C:\Company\Support\portqry>portqry -n 151.164.23.201 -e 53 -p BOTH
>
> Querying target system called:
>
> 151.164.23.201
>
> Attempting to resolve IP address to a name...
>
> Failed to resolve IP address to name
>
> querying...
>
> TCP port 53 (domain service): FILTERED
>
> UDP port 53 (domain service): LISTENING or FILTERED
>
> Sending DNS query to UDP port 53...
>
> DNS query timed out
>
> C:\Company\Support\portqry>
>
> any hope for me.

Check your firewall settings, it appears that port 53 is being blocked for
both TCP and UDP, both protocols are required.
What is the IP 192.168.100.2? Server? Router? Did you run this from the
server itself?

I tested this DNS server from Wichita Falls and it responded with all Root
Server NS records in 281 ms while my son is downloading a 13gb file from
Battle Net, so it's not a problem with this forwarder. It is sure to be
something blocking these ports in your firewall or router.

You should download Netdig and test response time to different DNS servers.

Here is a list of available SBC public DNS resolvers.
Southwestern Bell Internet Services Network Settings:
http://dialup.swbell.net/help/config.html



--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps

===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================


Re: recursive query fails
Freddie 21.06.2007 18:37:01

192.168.100.2 is the DC (server), 151.164.23.201 is the ISP's DNS
,192.168.100.1 is the Gateway(cisco 2811).
this was done on the server or the domain controler or the DNS (all in one
server)
i will try the to downlaod Netdig and try it

thanks again.

freddie

"Kevin D. Goodknecht Sr. [MVP]" wrote:

[Quoted Text]
> Read inline please.
>
> In news:384AB127-B452-4B00-B3F3-D44FF6C26AF4[ at ]microsoft.com,
> Freddie <Freddie[ at ]discussions.microsoft.com> typed:
> > this is what I am getting with your command
> > Microsoft Windows [Version 5.2.3790]
> > (C) Copyright 1985-2003 Microsoft Corp.
> >
> > C:\Documents and Settings\Administrator.SERVER>cd
> > C:\Company\Support\portqry
> >
> > C:\Company\Support\portqry>portqry -n 198.41.0.4 -e 53 -p BOTH
> >
> > Querying target system called:
> >
> > 198.41.0.4
> >
> > Attempting to resolve IP address to a name...
> >
> > Failed to resolve IP address to name
> >
> > querying...
> >
> > TCP port 53 (domain service): FILTERED
> >
> > UDP port 53 (domain service): LISTENING or FILTERED
> >
> > Sending DNS query to UDP port 53...
> >
> > DNS query timed out
> >
> > C:\Company\Support\portqry>portqry -n 198.192.100.2 -e 53 -p BOTH
> >
> > Querying target system called:
> >
> > 198.192.100.2
> >
> > Attempting to resolve IP address to a name...
> >
> > Failed to resolve IP address to name
> >
> > querying...
> >
> > TCP port 53 (domain service): FILTERED
> >
> > UDP port 53 (domain service): LISTENING or FILTERED
> >
> > Sending DNS query to UDP port 53...
> >
> > DNS query timed out
> >
> > C:\Company\Support\portqry>portqry -n 151.164.23.201 -e 53 -p BOTH
> >
> > Querying target system called:
> >
> > 151.164.23.201
> >
> > Attempting to resolve IP address to a name...
> >
> > Failed to resolve IP address to name
> >
> > querying...
> >
> > TCP port 53 (domain service): FILTERED
> >
> > UDP port 53 (domain service): LISTENING or FILTERED
> >
> > Sending DNS query to UDP port 53...
> >
> > DNS query timed out
> >
> > C:\Company\Support\portqry>
> >
> > any hope for me.
>
> Check your firewall settings, it appears that port 53 is being blocked for
> both TCP and UDP, both protocols are required.
> What is the IP 192.168.100.2? Server? Router? Did you run this from the
> server itself?
>
> I tested this DNS server from Wichita Falls and it responded with all Root
> Server NS records in 281 ms while my son is downloading a 13gb file from
> Battle Net, so it's not a problem with this forwarder. It is sure to be
> something blocking these ports in your firewall or router.
>
> You should download Netdig and test response time to different DNS servers.
>
> Here is a list of available SBC public DNS resolvers.
> Southwestern Bell Internet Services Network Settings:
> http://dialup.swbell.net/help/config.html
>
>
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This Helps
>
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
> http://www.lonestaramerica.com/
> http://support.wftx.us/
> http://message.wftx.us/
> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
> http://www.oehelp.com/OEBackup/Default.aspx
> ===================================
>
>
>
Re: recursive query fails
"Kevin D. Goodknecht Sr. [MVP]" <admin[ at ]nospam.WFTX.US> 21.06.2007 20:02:11
Read inline please.

In news:F638D57E-2655-4BA3-AA65-D0714CB80E39[ at ]microsoft.com,
Freddie <Freddie[ at ]discussions.microsoft.com> typed:
[Quoted Text]
> 192.168.100.2 is the DC (server), 151.164.23.201 is the ISP's DNS
> ,192.168.100.1 is the Gateway(Cisco 2811).
> this was done on the server or the domain controler or the DNS (all
> in one server)

Make sure the rules in the Cisco is setup to allow 53 TCP and UDP to any IP
address on the internet. It is not necessary to allow incoming connections
on those ports. Also, make sure the Cisco allows UDP packets up to 1500
bytes, some Cisco router/firewalls block UDP packets over 512 bytes which
effectively blocks EDNS used by Win2k3 DNS.

> i will try the to downlaod Netdig and try it

Good tool to use, it has a GUI interface which makes it much easier to use
than Nslookup without having to make all the unnecessary PTR lookups that
nslookup does. You do have to keep in mind it does not append suffixes,
you'll have to use valid DNS names, the first query you want to try is ".
ns" (without the quotes) which looks up the Internet Root Servers. Place it
on a local drive so you don't have to mess with configuring .NET Framework
trust.



--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps

===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================


Re: recursive query fails
Freddie 10.07.2007 21:50:02

is Netdiag not a Windows 2000 diagnostics?
when I download it and run it is giving me error message.
I do not think my problem is with DNS.
I had called CIsco tech people last week and explain the problem.
we check with all the settings. and they were ok.
now remember when I use dhcp on the Server, I can get the internet working.
but using a static DNS (server's local IP or even isp's IP), then I can not
get out.
only changes I saw between static IP and DHCP is the winserver.

this is a DHCP :
Microsoft Windows [Version 5.2.3790]
C:\Documents and Settings\Administrator.SERVER>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : server
Primary Dns Suffix . . . . . . . : XYANTTech.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : XYANTTech.local
xyant.com

Ethernet adapter Local:

Connection-specific DNS Suffix . : xyant.com
Description . . . . . . . . . . . : Intel(R) PRO/100 S Server Adapter #2
Physical Address. . . . . . . . . : 00-0E-0C-A9-FE-E1
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.100.75
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.100.1
DHCP Server . . . . . . . . . . . : 192.168.100.252
DNS Servers . . . . . . . . . . . : 192.168.100.254
68.12.16.25
151.164.23.201
Primary WINS Server . . . . . . . : 192.168.100.253
Secondary WINS Server . . . . . . : 192.168.100.254
Lease Obtained. . . . . . . . . . : Tuesday, July 10, 2007 3:58:46 PM
Lease Expires . . . . . . . . . . : Tuesday, July 10, 2007 11:58:46 PM

C:\Documents and Settings\Administrator.SERVER>

and if I use Static IP

(C) Copyright 1985-2003 Microsoft Corp.
C:\Documents and Settings\Administrator.SERVER>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : server
Primary Dns Suffix . . . . . . . : XYANTTech.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : XYANTTech.local

Ethernet adapter Local:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 S Server Adapter #2
Physical Address. . . . . . . . . : 00-0E-0C-A9-FE-E1
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.100.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.100.1
DNS Servers . . . . . . . . . . . : 192.168.100.2

C:\Documents and Settings\Administrator.SERVER>
Microsoft Windows [Version 5.2.3790]
does wins server giving the problem?
or I am out of luck?

thanks again
Freddie

"Kevin D. Goodknecht Sr. [MVP]" wrote:

[Quoted Text]
> Read inline please.
>
> In news:F638D57E-2655-4BA3-AA65-D0714CB80E39[ at ]microsoft.com,
> Freddie <Freddie[ at ]discussions.microsoft.com> typed:
> > 192.168.100.2 is the DC (server), 151.164.23.201 is the ISP's DNS
> > ,192.168.100.1 is the Gateway(Cisco 2811).
> > this was done on the server or the domain controler or the DNS (all
> > in one server)
>
> Make sure the rules in the Cisco is setup to allow 53 TCP and UDP to any IP
> address on the internet. It is not necessary to allow incoming connections
> on those ports. Also, make sure the Cisco allows UDP packets up to 1500
> bytes, some Cisco router/firewalls block UDP packets over 512 bytes which
> effectively blocks EDNS used by Win2k3 DNS.
>
> > i will try the to downlaod Netdig and try it
>
> Good tool to use, it has a GUI interface which makes it much easier to use
> than Nslookup without having to make all the unnecessary PTR lookups that
> nslookup does. You do have to keep in mind it does not append suffixes,
> you'll have to use valid DNS names, the first query you want to try is ".
> ns" (without the quotes) which looks up the Internet Root Servers. Place it
> on a local drive so you don't have to mess with configuring .NET Framework
> trust.
>
>
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This Helps
>
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
> http://www.lonestaramerica.com/
> http://support.wftx.us/
> http://message.wftx.us/
> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
> http://www.oehelp.com/OEBackup/Default.aspx
> ===================================
>
>
>

Home | Search | Terms | Imprint | Contact
Newsgroups Reader - provided by WiredBox.Net