Tag Info

New answers tagged

0

As I mentioned in a comment earlier, the addresses mentioned in the question belong to Google and therefore it's ultimately up to Google whether these addresses have a reverse PTR record or not. I haven't really dug into what exactly all of these addresses may be (maybe Pingdom made that information available to you?) but for instance 64.233.189.26 appears ...


1

Yes you can have multiple A Records that point to the same Public IP address and internal server. That is quite normal. The way to look at it is: Your exchange server runs both the autodiscover & the mail service so you can indeed have both pointing to the same exchange server.


1

DNS servers have cache, each change take time to be fully functional for all DNS servers. It may be fix in few hours. You can try nslookup -type=ns 64.233.162.26 to get a non cached answer


0

Where is your PDC FSMO currently held? This is the server you should use when running the command resetpwd /server:<PDC.domain.com> /userd:<Domain\domain_admin> /passwordd:* I'm assuming that the PDC FSMO is on DC2. My guess is that when you ran this on DC2 you used the servername as DC2 which is correct. However, when you ran this on DC1, you ...


0

There's the "Convert record names to canonical form?" option in the "Module Config" section of the BIND DNS Server module. Setting it to "no" yields the desired result.


1

If I understand you correctly you should just add multiple A-records for the given domain the clients are accessing. The DNS server will provide a random IP each time a client asks for it. It is also called round-robin DNS. Example: www IN A 127.0.0.1 www IN A 127.0.0.2 www IN A 127.0.0.3 www IN A 127.0.0.4


0

yoonix is correct, the "." on this line: @ IN NS romeo0. is not correct. Also, do you have an A record for romeo0? I'm guessing, but I think what you wanted is: IN NS romeo0.local.lan. romeo0 IN A 192.168.1.160 router IN A 192.168.1.1 romeo1 IN A 192.168.1.161 from: ...


0

After some research with ISP it turned out that answer to this riddle is: We were being caught by UDP Connection limit set on IP. Limit got taken down and everything works.


5

The error messages and the referenced RFC2181 5.4.1 pretty much already tells what's wrong: you are having conflicting NS records in your zone and in the parent zone as "glue" records. "Glue" above includes any record in a zone file that is not properly part of that zone, including nameserver records of delegated sub- zones (NS records), ...


1

Putting aside the $ORIGIN issue (which Vasili is 100% correct on), the RFC that defines the DNAME record type (RFC6672) actively discourages it. 3.3. Wildcards The use of DNAME in conjunction with wildcards is discouraged [RFC4592]. Thus, records of the form "*.example.com DNAME example.net" SHOULD NOT be used. The interaction between ...


2

This will simply not work, as the $ORIGIN must contain a valid zone name. A wildcard is not a valid zone name. At best, you can hope to script the creation of all of the zones you require in your BIND configuration, and point them all at the same generic zone file.


3

The immediate cause of error is the leading whitespace in your db.10 file. Correct: ; ; BIND reverse data file for local loopback interface ; $TTL 604800 @ IN SOA necacdnsone.necone.com. root.necone.com. ( 1 ; Serial 604800 ; Refresh 86400 ...


0

A good introduction to DNS related threats are given in RFC3833. Basically DNSSEC is one way among others to be sure that the server you are connecting is really legitimate. However, it is just one layer of security and not satisfactory on its own: it does not prevent re-routing your traffic to somewhere else or interpret the packets it they are not ...


0

I would say it essentially boils down to what you already mentioned. If you have DNSSEC implemented on both ends (a validating resolver and a signed zone), then DNSSEC prevents a man in the middle from altering the response without detection as well as avoiding the risk that a non-MITM attacker may win the what, for unauthenticated data, is a simple race of ...


2

First of all, I'm currently unable to reproduce the problem. I'm not sure if any of this actually answers the question (I'm not sure there even really is a clear question) but here is my take on what has been presented: named-checkzone is the tool appropriate for testing a zone file (named-checkconf is for the named configuration file). You should have ...



Top 50 recent answers are included