1. Dns Unknown Type 41

-->

Applies To: Windows Server (Semi-Annual Channel), Windows Server 2016, Windows Server 2012 R2, Windows Server 2012

changes the resource record type for the query.

Syntax

Parameters

Specifies a DNS resource record type. The default resource record type is A. The following table lists the valid values for this command.

Value	Description
A	Specifies a computer's IP address
ANY	Specifies a computer's IP address.
CNAME	Specifies a canonical name for an alias.
GID	Specifies a group identifier of a group name.
HINFO	Specifies a computer's CPU and type of operating system.
MB	Specifies a mailbox domain name.
MG	Specifies a mail group member.
MINFO	Specifies mailbox or mail list information.
MR	Specifies the mail rename domain name.
MX	Specifies the mail exchanger.
NS	Specifies a DNS name server for the named zone.
PTR	Specifies a computer name if the query is an IP address; otherwise, specifies the pointer to other information.
SOA	Specifies the start-of-authority for a DNS zone.
TXT	Specifies the text information.
UID	Specifies the user identifier.
UINFO	Specifies the user information.
WKS	Describes a well-known service.
{help	?}

Displays a short summary of nslookup subcommands

Crazy Egg.

Optimizely. HasOffers. Google Adwords. Google Tag Manager.

Remarks

• The set type command performs the same function as the set querytype command.
• for more information about resource record types, see Request for Comment (Rfc) 1035.

  additional references

  Command-Line Syntax Keynslookup set querytype

When using the nslookup command on a Windows 2008 R2 Core installation which also happens to be the primary DNS server and a DC for my domain, I sometimes receive the following error:
nslookup -querytype=ns microsoft.com 192.168.10.1
Server: ns0.chs.etc.corp
Address: 192.168.10.1
(root) ??? unknown type 41 ???

This only happens every now and then. Sometimes during the day I will receive a list of NS for microsoft.com but most of the time I just get the error. I use Microsoft System Center Essentials 2010 to monitor so that is how I know if it is working or not.
Also, in DNS configuration, I have forwarders turned on that point to two Ubuntu bind9 DNS servers that sit on my DMZ. Those servers then forward to DynDns servers.
Thank you in advance for any help.

I execute NSLOOKUP and see

C:>NSLOOKUP

Dec 30, 2015  Canon PIXMA iP90 Printer Driver Download for MAC. Rugged, powerful and portable, the Canon Pixma iP90 Photo Printer delivers exceptional performance at home or on the road. This compact printer can produce up to 16 ppm in black & up to 12 ppm in color, while achieving a resolution of up to 4800 x 1200 color dpi2.

Canon PIXMA iP90 Driver & Software Download For Windows, Mac – Movement, portable, or whatever thing you call it is something that many people are looking nowadays and this is one thing that Canon PIXMA iP90 offers for all of the people who need the best printing prom printing from many different places that they want. This printer is considered as one great development in this kind of. Dec 15, 2017  Canon PIXMA iP90 Driver Download - iP90 Photo Printer is always given an extraordinary performance both for the work at home or on the road. This very compact printer can work and produce up to 16 ppm in black and up to 12 in color, it is remarkable indeed, while to achieve a resolution of up to 4800 x 1200 color dpi display pictures.

Default Server: UnKnown

Address: 192.168.1.1

I am guessing that it should be something like

C:> nslookup

Default Server: nameserver1.domain.com

Address: 192.168.1.1

How to fix it?

Could it be the reason why I cannot ping the Domain Controller by its full name?

P.S. Network settings of the workstation

Ethernet adapter Local Area Connection:

Developer

DeveloperDeveloper

16711 gold badge33 silver badges1414 bronze badges

closed as unclear what you're asking by Ƭᴇcʜιᴇ007, Kevin Panko, Der HochstaplerDec 16 '13 at 9:48

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

1 Answer

It appears you are using a basic router/gateway device as your Gateway, DHCP and most importantly DNS (192.168.1.1).

Assuming that, then that router is not a real DNS server, and is actually just forwarding your DNS requests to the DNS server setup in the WAN-side of the router.

Since the router is not a real DNS server it has no name (or at least it doesn't report a name when queried), so NSLookup doesn't know its name and instead reports 'unknown' as the name.

Try using a specific DNS server with NSlookup, like say Google's (8.8.8.8):

nslookup - 8.8.8.8

(using - instead of a host name puts NSLookup into interactive mode like just a plain nslookup does, except using Google's DNS server for queries).

That command should return something more like what you expect:

Default Server: google-public-dns-a.google.com
Address: 8.8.8.8

Dns Unknown Type 41

Your question 'Could it be the reason why I cannot ping the Domain Controller by its full name?' is hard to answer, as you haven't provided any real information on the setup of your network. If you are trying to setup an actual Active Directory domain, and contact an actual AD 'Domain Controller', then you need to reconfigure this client to properly use the AD-integrated resources (DNS, DHCP, etc.) instead of the gateway device.

Ƭᴇcʜιᴇ007Ƭᴇcʜιᴇ007

101k1616 gold badges160160 silver badges225225 bronze badges

Not the answer you're looking for? Browse other questions tagged dnspingdomainnslookup or ask your own question.

Posted by3 years ago

Archived

EDIT: Solved. See top thread. Thanks all!

So this is strange and I'm not even sure that it's breaking anything as my internet works fine on clients and the server but I can't do a successful nslookup on any of my clients without getting 'DNS request timed out. timeout was 2 seconds.'. Nslookup on the server works fine.

• Server 2012 R2 Essentials running DHCP/DNS (ipv4 dhcp only, ipv6 handled by router)
• Forward lookup configured for ipv4/6 with google dns and isp dns as fallback
• Reverse lookup zones configured for ipv4/ipv6 with PTR records set
• Server configured to use itself for primary/secondary dns
• Clients configured to use server as only dns

If I specify the DNS server in the nslookup command explicitly, it works fine (nslookup google.com dnsServerName) and I get an immediate answer. Without, nothing works, even if I try using the FQDN.

Things I've tried:

• clear dns cache on both server/client (ipconfig /flushdns and clear cache via dns control panel on server)
• reset winsock (netsh winsock reset)
• reset tcp/ip stack (netsh int ipv4 reset)
• ipconfig /registerdns (on clients) Fallout 4 hair mods xbox.
• disabled firewall on server/client

At this point I'm out of ideas and reached the limit of my layman's understanding of dns. I can provide more details as necessary but am hoping I'm just missing something obvious as I've poured a considerable amount of google time into this issue with little to show for it.

20 comments