DNS Issue - nslookup resolve to random localhost ip
Hello all, I am new here. hope there is someone will help me. Please help me to resolve this issue. the host domain upxxxxx.edu.my can be resolve using public DNS. but while using internal DNS it will resolve to random localhost IP. i had restart the DNS/AD server. i made nslookup again after reboot then it appear127.118.0.45 (other local IP address). *this is new fresh install windows server 2022 std with AD, DHCP and DNS roles. thank you for your help. i am very appreciate the effort.
Strange DNS problem on Server 2022
I installed a new Server 2022 DC on my network as the only DC. It serves DNS for our network and for a few weeks all has been working fine. However, lately I have been having a problem using Outlook to access my secondary email address at comcast.net. For long periods the attempt to download email fails. I did some checking and found that when I do a nslookup on imap.comcast.net I get this: Non-authoritative answer: Name: imap.comcast.net (note, there are no IP addresses) If I do the same but specify Google's DNS server (8.8.8.8) I get: Non-authoritative answer: Name: imap.ge.xfinity.com Addresses: 2001:558:fc0a:3:f816:3eff:fea5:2243 2001:558:fc0a:3:f816:3eff:fe95:679f 2001:558:fc0a:3:f816:3eff:fe0c:7c51 2001:558:fc0a:3:f816:3eff:fe51:b939 2001:558:fc0a:3:f816:3eff:fee8:1979 2001:558:fc0a:3:f816:3eff:fe6b:52a6 2001:558:fc0a:3:f816:3eff:fe5d:49ac 2001:558:fc0a:3:f816:3eff:fe84:7ff1 2001:558:fc0a:3:f816:3eff:fef5:7c75 2001:558:fc0a:3:f816:3eff:fe8d:2a36 2001:558:fc0a:3:f816:3eff:fe57:df5e 2001:558:fc11:9:f816:3eff:fee9:ffd6 2001:558:fc11:9:f816:3eff:fedd:4bc5 2001:558:fc11:9:f816:3eff:fe40:d128 2001:558:fc11:9:f816:3eff:fec1:ef59 2001:558:fc11:9:f816:3eff:fe48:d86d 96.118.18.255 96.118.18.251 96.118.18.249 96.118.18.240 96.118.18.254 96.118.17.101 96.118.17.82 96.118.18.242 96.118.19.1 96.118.19.5 96.118.18.230 96.118.17.194 96.118.18.11 96.118.19.0 96.116.224.191 96.116.224.174 Aliases: imap.comcast.net
dns sortorder bug introduced over 10 years ago
As of Windows server 2012 there was a sort order bug introduced in the dns manager. All info is treated as a tekst string eventhough they are not. Therefore ip numbers are sorted wrong, dates are sorted wrong and managing the dns sometimes becomes a nightmare when sorting is needed. The solution is so simple, sort the original numbers, an ipnumer is a 32bit number. A timestamp is a number respresenting seconds after a start time. Please fix this so 2 comes after 1 and not after 19 or 199, etc. 1 January2024 does NOT follow 1 Jan 2024, there is a whole year of 364 other days in between. Neither does ip number 11.2.3.4. follow 1.2.3.4, nor does 111.2.3.4 😞 I and others have started reporting this bug as soon as it appeared but everytime we got answers like export to Excel (does not help) and other non answers. How hard is it to fix this? Today I need to delete some old dns records that were not properly scavaged. I CANNOT sort on timestamp to get all old records together. 😞
Trouble with DNS server
Good morning and sorry for my bad english 🙂 I have 2 AD/DNS servers in 2016. In terms of DNS cleaning, it is configured to clean records older than 7 days. The configuration is good at the server level and on the DNS zones. When I run a cleanup manually, I see that it works because I have event ID 2501 with deletion records. I simply have a lot of very old DNS records, which are not static, dating for example from November and which remain. I don't understand why they are not deleted.... Any idea to understand where the problem comes from? THANKS
Event 5775, NETLOGON
I am getting the following in System Event Viewer: ThedescriptionforEventID5775fromsourceNETLOGONcannotbefound.Eitherthecomponentthatraisesthiseventisnotinstalledonyourlocalcomputerortheinstallationiscorrupted.Youcaninstallorrepairthecomponentonthelocalcomputer. Iftheeventoriginatedonanothercomputer,thedisplayinformationhadtobesavedwiththeevent. Thefollowinginformationwasincludedwiththeevent: gc._msdcs.domain.local.600INA172.28.240.10 %%4294967295 172.28.254.10 5 4294967295 Thelocalespecificresourceforthedesiredmessageisnotpresent ThedescriptionforEventID5775fromsourceNETLOGONcannotbefound.Eitherthecomponentthatraisesthiseventisnotinstalledonyourlocalcomputerortheinstallationiscorrupted.Youcaninstallorrepairthecomponentonthelocalcomputer. Iftheeventoriginatedonanothercomputer,thedisplayinformationhadtobesavedwiththeevent. Thefollowinginformationwasincludedwiththeevent: _gc._tcp.domain.local.600INSRV01003268nap-dc-p01.domain.local. %%4294967295 172.28.254.10 5 4294967295 Thelocalespecificresourceforthedesiredmessageisnotpresent I was trying to open the Group Policy Management on this DC (not the primary DC) and I was getting this message: The other DC at this location is experiencing the same issue, yet 3 in 2 other areas are working fine. Could this be a routing issue in the Firewall?
Internal DNS for SaaS Tool?
We're using a SaaS tool where we are able to have it accessible via our domain name. support.mydomain.com goes to me.tooldomain.com via CNAME record. The DNS entry is identical on our external DNS (Cloudflare) and internal (Server 2019). This works perfectly fine outside of our LAN. However, on our LAN if users try going to support.mydomain.com they get a "NET::ERR_CERT_COMMON_NAME_INVALID" in whatever browser they use. Specifically it's saying that the server could not prove it is support.mydomain.com and that it's security certificate is from *.tooldomain.com. This happens with all major web browsers. I just don't understand why we're only having problems on the LAN side, and the DNS records are identical. Any help would be greatly appreciated.How to sort out a reverse DNS mess
Hi, Our organization has a number of 10.X.0.0/16 locations with the same AD/DNS name ourcompany.com. No worries. We are connected to a separate company with the AD/DNS name othercompany.com who were using some 172.16.XXX.0/22 addresses. Still good. We used conditional forwarders on each companys DNS records to forward each others forward and reverse lookup queries to the other. Great. But now, othercomapny.com is moving over to 10.X.0.0/16 network ranges. We have hit a snag on the ourcompany.com DNS server in that the reverse lookup zone is 10.in-addr.arpa instead of each individual X.10.in-addr.arpa zone. This means the ourcompany.com DNS server cannot create a conditional forwarder for 44.10.in-addr.arpa as this overlaps with our 10.in-addr.arpa zone. As a result we cannot reverse lookup othercompany.com IP addresses. Deleting our reverse lookup zone 10.in-addr.arpa sounds pretty horrifying, so I am wondering is there a best approach to doing this? Is it possible at all? I appreciate any advice anyone can give.
DNS Delegation Issue- Automatically Changing the FQDN of authoritative name servers to IP addresses.
Hi Members, Currently, I am facing a strange issue with DNS Delegation. We have created a Delegation record in DNS using theauthoritative name servers FQDN and when we created this Delegation was working as expected. A few months later suddenly application team reported an issue saying the DNS was not able to resolve the URL. When we verified the URL Deligation record, we found that the record was modified with an authoritative name server's IP address instead of FQDN in the server FQDN place and the IP address was showing as 'unknown'. To fix the delegation issue we have re-created the Delegation record with FQDN again and the issue got fixed. We have verified the DNS Audit logs and system logs we couldn't identify any logs saying the Delegation records got modified with IP address after it was created originally. And we have identified the same issue with a few other delegation records as well... So how did the record got modified automatically? Theauthoritative name servers are having proper A records created in DNS so why it was showing as 'unknown' when the issue was reported? When we ran adcdiag /test:DNS test it reported a few numbers of 'Broken delegated domain' errors but when we verified those delegation records manually those are working fine without any issues. If anyone faced similar issues or knows any reason why "FQDN of authoritative name servers automatically chnage to IP addresses in a delegation record" Kindly help me to identify the root cause. Thanks in advance. Server:Microsoft Windows Server 2019 Standard 10.0.17763 N/A Build 17763. DNS Build version:4563000A (10.0 build 17763)DNS Query Policy to make DNS server authoritative for a single host in Domain
I wish to do the following with my Windows 2016 DNS server: Forward all queries for test.fwd to another DNS server except for a handful of records to which I wish to be authoritative i.e. host1.test.fwd Would this be possible with a DNS Query Policy?
