Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
the main domain is www.abc.com
I use the DNS to set all sub-domains *.abc.com point to the www.abc.com.
How to say this in english?
I find the wikis, is it correct for 'pan-domain name resolving'
Wildcard DNS records Main article:
Wildcard DNS record The domain name
system supports wildcard domain names
which are names that start with the
asterisk label, '*', e.g.,
*.example.[3][17] DNS records belonging to wildcard domain names
specify rules for generating resource
records within a single DNS zone by
substituting whole labels with
matching components of the query name,
including any specified descendants.
For example, in the DNS zone
x.example, the following configuration
specifies that all subdomains
(including subdomains of subdomains)
of x.example use the mail exchanger
a.x.example. The records for
a.x.example are needed to specify the
mail exchanger. As this has the result
of excluding this domain name and its
subdomains from the wildcard matches,
all subdomains of a.x.example must be
defined in a separate wildcard
statement. The role of wildcard
records was refined in RFC 4592,
because the original definition in RFC
1034 was incomplete and resulted in
misinterpretations by
implementers.[17]
Wildcard DNS record
I think this the computer-specific term which I searched for.
I want to build a wildcard dns resolving in my local-network for windows environment...
I'm search for a tutorial....
Any suggestions?
Thanks for your reply!
I think you're looking for wildcard DNS records.
http://en.wikipedia.org/wiki/Wildcard_DNS_record
I don't understand exactly what you mean. You could set CNAME records on them and point it to www.abc.com, but I don't know if that's what you mean.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 12 months ago.
Improve this question
I read a document which says that a host with a complicated hostname can have one or more alias names. For example, relay1.west-coast.media.com is a canonical hostname whereas media.com is an alias. They both are related with each other by 'A' record and 'CNAME' record in DNS system follows:
media.com CNAME relay1.west-coast.media.com
relay1.west-coast.media.com A 210.23.25.32
What makes us use the complicated canonical hostname? Can't we simply associate alias with the ip address by adding record 'A' in the DNS system as follows:
media.com A 210.23.25.32
CNAME entries are useful when running multiple services on a single server. For example you could point www.media.com, ftp.media.com, and mud.media.com all to relay1.west-coast.media.com.
That way if the IP address of relay1... ever needed to change, it would be a single update to the A record instead of multiple.
Yes, you can.
First, as Lanexbg explained your specific example is wrong since you can not have a CNAME at apex (root) of the zone because by definition a CNAME record can not coexist with anything else (we will forget about the exceptons here) and at apex you need to have SOA and NS records for your zone to work correctly.
So let us just instead use the appropriate names for configuration/documentation needs and discuss about the difference between www.example.com A and www.example.com CNAME www.example.net + www.example.net A
The end result of the www.example.com A resolution would be the same for an end user, besides various points that can be neglected on a first approach (like performance issues).
If you are maintaining both the authoritative nameservers for example.com and example.net you are free to choose between the two cases. As Chris Meueur noted, the big difference is when you need to change the data (IPv4 address) of the A record. In the first case you will need to change it as many times as you have records for it where in the second case you will need to change it only once, and all other records having a CNAME pointing to www.example.net will get automatically updated.
CNAME have their drawbacks too: they can influence performance, you need to avoid chains of them and even more loops, they can not be used everywhere in the same way as a name in an A record, etc.
So it is a compromise.
But there is another case to take into account: if you are the administrator of example.com but not of example.net. ExampleNET Inc. could be a big hosting company, or a CDN. You want to use their services for your www.example.com website. If they give you an A record to put in your zone they have the problem that they will basically never be able to change it if they need because all their clients will have its current value hardcoded in all their zonefiles, so that is a big problem against agility, and sometimes you need to be able to renumerate in an hurry, like during a DDOS attack.
Instead if they advise you to do a CNAME, they would be free to change their A record without anything else having anything to do and with the results "immediately" applied to everyone.
This is a very common case, specifically for CDN.
Among many others see this live example when asking for www.microsoft.com:
;; ANSWER SECTION:
www.microsoft.com. 3600 IN CNAME www.microsoft.com-c-3.edgekey.net.
www.microsoft.com-c-3.edgekey.net. 20499 IN CNAME www.microsoft.com-c-3.edgekey.net.globalredir.akadns.net.
www.microsoft.com-c-3.edgekey.net.globalredir.akadns.net. 3600 IN CNAME e13678.dspb.akamaiedge.net.
e13678.dspb.akamaiedge.net. 3600 IN A 23.67.120.106
(of course advanced setups can also be enable for load-balancing and/or fail-over and/or varying the result based on the geography of the source).
This is not the only way to do it (for example, instead, they could have asked you to change the authoritative nameservers for your example.com zone so that they could control it), and it has limits too (the most important one being the one outlined at the beginning: you could not put a CNAME at apex so if you wanted also a website on http://example.com/ (note the lack of www) you would need other solutions).
I think media.com could have different sub-domains under the actual domain, for example - www.media.com, ftp.media.com, mud.media.com these are some of the sub-domains under media.com. Each and every sub-domain will have a different IP address also, so if we just point it to media.com A 210.23.25.32, it won't be able to resolve the full query that the user needs.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 6 years ago.
Improve this question
I have a website hosted running on a VPS. I can access the site via the browser with an IP address. I want to be able to access it using the domain name i have with GoDaddy.
So far I have added a host name in GoDaddy.NS1.MYDOMAIN.COM = IP address. I did this yesterday and when I look up the name-servers for my domain on who is the new host-name I made in GoDaddy is showing up as the first name-server for the domain but its pointing to the ip of the old host.
The VPS is hosted with OVH. A tutorial on the site says to enter the first name-server based on my account number E.G. nsXXXX.ovh.fr. I tried this but GoDaddy returns an error saying "You must enter a registered name-server".
GoDaddy wont let me edit anything in the DNS zone file tab because it says the name-servers aren't pointing at it.
Sounds like you changed the nameserver address of your domain instead of adding a host record which it sounds like was your intention.
You should let GoDaddy run your name servers (unless you plan on having your DNS hosted elsewhere). Then you will be able to edit the zone file and add an A record for your domain.
Step 1:
Under Settings tab, Nameservers click manage and make sure Standard is selected.
Step 2:
Under DNS Zone File (assuming you can now edit this) click Add Record.
Record type: A (Host)
Host: yourdomain.com
Points to: your IP address
TTL: Leave default (1 hour)
Make sure you save your changes.
Might take a few hours to propagate so don't panic if it doesn't work immediately.
'Setting up DNS with Your Parallels Plesk Panel 11 Server and Domain with Us' may be helpful to you. Here's a link: Setting up DNS with Your Parallels Plesk Panel 11 Server and Domain with Us.
Link to file
http://support.godaddy.com/help/article/8463?locale=en&ci=46061
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I'm a newbie to hosting. Please bear with me.
I bought a new Virtual Server with my host GoDaddy. I want to setup my own DNS and point one or more domains to that server.
I have 3 IP addresses allocated to me. Lets assume them to be 10.0.0.1, 10.0.0.2 and 10.0.0.3. Lets assume the name of my server is "mydomain". This is what it shows when I right click on My Computer and go to Properties and see Full Computer Name. I have already installed the DNS role on this server.
What I want is to create DNS like ns1.mydomain.com and ns2.mydomain.com. Then I want to configure www.otherdomain.com to this server.
Can someone guide me on how to do the above.
Many Thanks,
Arun
If you wish to host the DNS on your own server you will have to register your nameservers with your domain registrar first. If this is Go Daddy you will use these steps:
Log in to your Account Manager.
Next to Domains, click Launch.
Click the domain name you want to use to register as your own nameserver.
In the Host Summary section, click add.
In Host name, enter the host name you want to register. This would be something like "ns1". The value entered here will be appended to your domain name to create the host name. Do not use the 'www' prefix. Example: For the domain name coolexample.com, entering 'ns1' here results in ns1.coolexample.com.
In the Host IP fields, enter the IP address for your server.
Click OK.
Once you have the two nameservers setup you can point your domains to the server using these. You will need to ensure that the Zone File for the domain you setup the nameservers on will have A records for ns1 and ns2 as well. If you host the domain on your server you would edit the Zone File on the server and add those A records. If you do not point the nameserver domain to your server you would just to this in the DNS editor in the Domain Manager.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
We are hosting the page of many of our customers. We want to be able to provide our customers with a subdomain of our own domain like customerpages.ourdomain.com so they can create a CNAME to this subdomain.
www.customer1.com CNAME customerpages.ourdomain.com. {This will work just fine.}
But the situation is I don't know if all our customers will be able to place the following CNAME
customer1.com CNAME customerpages.ourdomain.com
This last CNAME looks like it's against the RFC of DNS.
Any thoughts will be appreciated.
No, you can't do that - CNAME records can only exist as single records and not combined with any other resource record (DNSSEC records excepted).
There are explicit SOA and NS records always present at the top of each domain, so that prevents the use of the CNAME at the same part of the hierarchy.
It's true, given a domain example.com, some DNS servers (tinydns for one) won't complain if you set up CNAME records for both example.com and www.example.com. But still I'd avoid it as it would break e-mail for example.com (see RFC 2821 "Address Resolution and Mail Handling").
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I want to find out all the subdomains of a given domain. I found a hint which tells me to dig the authoritative Nameserver with the following option:
dig #ns1.foo.example example.com axfr
But this never works. Has anyone a better idea/approach
The hint (using axfr) only works if the NS you're querying (ns1.foo.example in your example) is configured to allow AXFR requests from the IP you're using; this is unlikely, unless your IP is configured as a secondary for the domain in question.
Basically, there's no easy way to do it if you're not allowed to use axfr. This is intentional, so the only way around it would be via brute force (i.e. dig a.example.com, dig b.example.com, ...), which I can't recommend, as it could be viewed as a denial of service attack.
If you can't get this information from DNS (e.g. you aren't authorized) then one alternative is to use Wolfram Alpha.
Enter the domain into the search box and run the search. (E.g. stackexchange.com)
In the 3rd section from the top (named "Web statistics for all of stackexchange.com") click Subdomains
In the Subdomains section click More
You will be able to see a list of sub-domains there. Although I suspect it does not show ALL sub-domains.
You can use:
$ host -l example.com
Under the hood, this uses the AXFR query mentioned above. You might not be allowed to do this though. In that case, you'll get a transfer failed message.
dig example.com soa
dig #ns.SOA.example example.com axfr
robotex tools which are free will let you do this but they make you enter the ip of the domain first:
find out the ip (there's a good ff plugin which does this but I can't post the link cos this is my first post here!)
do an ip search on robotex: http://www.robtex.com/ip/
in the results page that follows click on the domain you're interested in>
you are taken to a page that lists all subdomains + a load of other information such as mail server info
You can only do this if you are connecting to a DNS server for the domain -and- AXFR is enabled for your IP address. This is the mechanism that secondary systems use to load a zone from the primary. In the old days, this was not restricted, but due to security concerns, most primary name servers have a whitelist of: secondary name servers + a couple special systems.
If the nameserver you are using allows this then you can use dig or nslookup.
For example:
#nslookup
>ls example.com
NOTE: because nslookup is being deprecated for dig and other newere tools, some versions of nslookup do not support "ls", most notably macOS X's bundled version.
In Windows nslookup the command is
ls -d example.com > outfile.txt
which stores the subdomain list in outfile.txt
few domains these days allow this
If the DNS server is configured properly, you won't be able to get the entire domain. If for some reason is allows zone transfers from any host, you'll have to send it the correct packet to make that request. I suspect that's what the dig statement you included does.