Tag Info

New answers tagged

0

CNAME won't work. You can't even create a CNAME www.microsoft.com pointing to host.yourdomain.local because you are not hosting the domain "microsoft.com". You can create a subzone called "microsoft.com", then a CNAME called "www" pointing to your own host.yourdomain.local. But then your internal users who use your DNS for name resolution won't be able to ...


0

It does look like port 25 open outwards, but possibly not in the other direction, try a site like this http://www.mynetworktest.com/ports.php or this http://www.canyouseeme.org and test port 25 to your servers' external IP address. If it fails, you may have a firewall or ISP configuration issue still.


-2

Thanks Ryan... I posted this question as I was at this all day then realised that time is a great healer. I have just checked and all records have been populated again. The magic of time itself. Cheers for the answer though.


-1

Try to disable IPv6 configuration at the ethernat adapter and you are able to list your server correctly


0

ok, I found a solution, its not perfect, but I supposed it is the conventional solution. While trying to change the computer name to something else, I noticed there's an option to add a suffix, it did helped me to solve the problem. these are the following steps. 1. Control Panel > System & Security > System 2. click on "Change Settings" for ...


1

By default, the value of parameter smtp_host_lookup is dns. Because of that, postfix will always try to resolve the MX record recipient domain to determine the next-hop destination. Postfix rely on libc resolver to do the lookup so the expected behaviour would depends on the library. For example, postfix will alwasy do lookup via NS server defined in ...


0

Depending on what access level you have to your hosting environment and if you are running an Apache web server you may also be able to use Apache VHosts service. See this article: domain redirection with virtualhost


0

You need specific software to perform this, and it is considered Evil. Breaking the Internet by performing a man-in-the-middle attack on DNS traffic is exactly why things like DNSSec are being rolled out. If you're intent on looking though, you might want to check results for "DNS Interception" and "Transparent DNS Proxy". Some things that come to mind are ...


0

I ended up using mysql galera cluster instead with all 3 power dns servers set as master, works like a charm


2

Your host does not seem to be caching dns lookups. It should be. No Your operating system (not postfix) should cache every DNS record lookup it needs. NSCD is one common tool to cache "hosts" queries.


4

No, those IPs don't belong to your ISP. They cannot change that, they belong to CloudFlare. You don't need a reverse DNS record for normal HTTP/HTTPS browsing. You could contact CloudFlare but I doubt they will configure it. Those IPs are shared between many customers.


0

Remove "destination" from the function arguments. From https://doc.powerdns.com/md/recursor/scripting/, preresolve() takes only three arguments preresolve ( remoteip, domain, qtype )


1

You've added the records for a subdomain @.example.com instead of just plain example.com. While the use of @ to represent the root is a common syntax in some DNS tools, it's not supported in Route53. Adding the records with an empty Name field will place the records on the root of the domain.


2

Which (if any) public TLDs permit for such subdomain configuration? They all should. However some registrars may prevent it due to restrictions in their web UIs. You should consider this a bug and complain. It would be useful if you reported any registrars you find doing this. How many DNS requests, pertaining to the domain, will be served by ...


2

What you're asking is largely opinion based, which isn't a good way to approach the problem. What you should be more concerned with are what the standards have to say. Considering the fact that nothing has emerged to obsolete BCP91, I think you would be best served by reading the document in full. Section 1 explains the problem in detail, but to avoid ...


2

All TLDs should support this, however for the near future having a DNS server with a v6 only address would have too many limitations.


0

To be honest, the zone foo (or example.com as someone later edited) was really wpad. Therefore I needed to remove wpad from the globale DNS block list applied.


0

You edit your DNS record(s) to point to your EIP.


6

Not quite. Every DC/DNS server hosting AD-integrated zones should contain '127.0.0.1' in its list of DNS servers, but only as the last entry. Ideally, you want the "Preferred DNS" to be a different DC in the same site, followed by a different DC in a different site if possible, and then localhost at the end of the list. In your case where you only have 1 ...


5

You are tackling this problem at the wrong layer. Literally, layer 4 when you should use layer 7. Don't log TCP connections in iptables. Instead, capture HTTP traffic and inspect the Host header in the requests that the clients are making.


7

I'm not sure i get the whole picture but since you are writing about websites i think you are using a tool that is not exactly suitable for the task. imho you are looking for that information (the visited domain name) at the wrong level: you should have a proxy and analyze its logs to gather that info. A proxy is 'near' the client and has the exact and ...


5

You cannot easily determine what the user typed into their browser's URL bar using just an IP address log: You can't tell if someone accessing 104.16.13.13 got there by typing aviation.stackexchange.com or tex.stackexchange.com (the best you can determine is that it's a CloudFlare IP address). In order to get the information you seek you would need to ...


2

No, it is not authoritative for the name which you asked for in the query. It is authoritative for one of the parent zones, though. Yes, it's authoritative for all names inside the zone that has been delegated to it (whether there are any records or not). Yes, if it's authoritative for example.com it's also authoritative for subdomain.example.com unless the ...


3

Basically, nevermind if your are using DHCP or not. Using a single DC in your domain, you have to make it a DNS Server also. Install and configure DNS role on your Domain Controller. Then configure your clients' DNS to point to the IP Address of your DC. The most important thing is that you have to setup your DNS Server to forward unknown names queries to ...


5

I assume you're using DHCP, right? Use DHCP to specify the default gateway and DNS servers. You can even use DHCP on your DC and keep it all in one place. DNS should be provided by the domain controller(s). They can forward unknown requests to your ISP's DNS servers.


1

All of these answers have some validity to them, but I think it really depends on what you are doing and what your budget is. Here at CloudfloorDNS, a large percentage of our business is DNS, and offering not only fast DNS, but low TTL options and DNS failover. We wouldn't be in business if this didn't work and work well. If you are a multinational ...


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 ...


0

We had the same problem, and we found out that our hardware showed broken behaviour with IPv6. You could double check with curl and force IPv4 like so: $ time curl -4 www.google.com ... real 0m0.074s user 0m0.011s sys 0m0.000s Update 1: We had the problem with our Windows Host System (Ubuntu 14.04 is the guest). The actual solution was found ...


1

First off, give us more information on what's not working. Are you getting the website for www2.example.com? A DNS error? 404 Page? something completely different? Some things to check on: Make sure DNS is resolving properly. You may need to clear your cache. Ping www2.example.com, and make sure you're getting the correct IP address. Otherwise, your ...


3

You may want something like this: example.com WWW A 192.0.2.1 WWW2 CNAME WWW2.example.net. example.net WWW2 A 192.0.2.2 This will make www.example.com go to 192.0.2.1, while www2.example.com will go to 192.0.2.2.


0

I think the real issue is that the domain name is a single-label DNS name (one word (billsgs) and then a valid tld (.net)). By default, DNS clients will not register with these domains because they are likely to be public domains. https://support.microsoft.com/en-us/kb/300684 has instructions to override that.


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


2

It's not completely clear what your overall plan entails but here are some clarifications about how wildcard records work in general. I think this should clarify what may potentially be a problem. Wildcard records do not cover the base name (ie *.example.com. does not cover example.com.). Wildcard records never overlap with anything, whether CNAME or any ...


0

Note: This answer is potentially incomplete as is. I've tried to add as much information as I could find to help carry the torch as far as possible, but I've added it as a community Wiki in hopes that other users will update incomplete or incorrect information. According to the question DNS debug log dns.log Format Review, the fields map as follows ...


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.


0

Glue is needed when the name servers for a given domain e.g. example.com are host names inside that domain, e.g. ns1.example.com. Without that glue it would be impossible to resolve anything inside example.com. In fact you should try to avoid situations where glue is necessary, as a misconfiguration where the glue is erroneously omitted from the zone will ...


5

Either v=spf1 a ~all and v=spf1 ip4:IP_OF_A_RECORD ~all would be suitable entries for a mail server. However the ~all negates most of the value of having an SPF record. Use of -all would be much better, and would be suitable for the entry for a mail server. With rare exceptions, no other server should be sending email on behalf of a mail server. The a ...


0

@Ankh2054 - Great answer! Make certain that you clarify that you're only transferring A records with your script. ( my apologies for not commenting directly, I can't comment on posts yet ) While in windows in an inside environment using AD you usually have the SRV records created by AD, MX records are commonplace. NS records are pretty big as well, even ...


0

we have upgraded our DNS server as Slave in 2003 Domain server environment. I know you mentioned about not being in domain environment but I don't think that would be an issue as long as you have access/admin rights to Master DNS server. Once the new 2012 server is configured with DNS role, you will get an option at one stage to replicate from Master DNS ...


2

Configure the DNS server on your domain controller to use the public Comcast IP addresses as forwarders only, or allow your DC to use the root hints. All other devices on your network should point to the DNS server on your DC. Your DCs should then point to itself in the network properties. Once this is all squared, the client that you're trying to add ...


2

Edit: Please note the below only transfers A records and no other so you would still need to manually input remaining. I've never done the above, but another alternative would be to: export your A records and zones from 2003. Save it - c:\dnsrecords.txt re-importing into Server 2012. Replicate other 2003 settings on 2012 that covers external lookups. ...


2

I've replicated this way before. It's just a zone transfer, really. I had to do it as part of a migration to new 2008 DC's in preparation for raising the functional level and replacing old hardware. The issue I had with 2003 was ad-integrated DNS not playing nicely. May have simply been because this domain had been an upgrade from NT 4.0 -> win2k -> ...


2

I thought I recognized those DNS IP numbers. You have DNS set to use Comcast's DNS, not the DNS that knows anything about sheptock.local. Change the workstation's DNS server to one that knows about steptock.local, including the DC for sheptock.local, and that should help. You can probably do this in your aforementioned wireless router if you're using it ...


-1

You cannot ping Windows 2012 Servers unless you enable it under the Windows Firewall by enabling the File and Printer sharing (Echo request – ICMPv4-In) rule (http://blog.blksthl.com/2012/11/20/how-to-enable-ping-in-windows-server-2012/). You should also check the firewall rules about Active Directory Domain Services.


4

It seems that you have created an additional zone for your blog.countdownevents.com. since it has independent SOA and NS records: ;; QUESTION SECTION: ;blog.countdownevents.com. IN SOA ;; ANSWER SECTION: blog.countdownevents.com. 3600 IN SOA ns15.domaincontrol.com. dns.jomax.net. ...


-1

In AIX you can use IP Alias to solve this. Let say you current IP address is 10.5.1.98 and your new IP address is 90.4.12.67 then you can define the 10.5.1.98 as an alias on top of 90.4.12.67. This way any server referencing the IP address 10.5.1.98 would be forwarded to 90.4.12.67 automatically. Whatever flavor of UNIX you are using or Linux for that ...


2

This cannot be done using DNS directly. A domain name always resolves to a single IP address, the port isn't related to DNS records at all. However, you can set up a reverse proxy on your web server that is listening on port 443. You would set up virtual hosts server.machine.com and other.machine.com on the www.machine.com web server, which would then ...



Top 50 recent answers are included