Closed. This question is not about programming or software development. 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 6 months ago.
Improve this question
I know thats not the kind of question that are commonly asked in here, but I don't know where to ask instead.
I want to setup DynDNS with my FritzBox 6600 Cable, but i always got an 500 - notfqdn (not full qualified domain name) Error. (I know FritzBox is not the best solution avaiable... but this is what i have to work with).
According to this guide i set up the DynDNS config in the FritzBox and used the username and password from the configured DynDNS and the update url domains.google.com/nic/update with the dyndns domain. The config in the FritzBox looks like the following:
Update-URL: domains.google.com/nic/update
Domainname (Domain-Name): something.my-domain.de
Benutzername (Username): my_username
Kennwort (Password): my_password
I don't know what's the problem. Some testing with other configuration shows that a random user and password give the same 500 error.
Do anybody know how the request of the FritzBox looks like and how the parameters are parsed?
According to the FRITZ!Box help page you can use pre-defined placeholders inside the Update URL which will be filled with the corresponding information.
So in the case of Google Domains the API expects a request URL in the following form:
https://username:password#domains.google.com/nic/update?hostname=subdomain.yourdomain.com&myip=1.2.3.4
In your FRITZ!Box DynDNS configuration you have to replace the variables in the Google Domains API URL by the corresponding placeholders from the FRITZ!Box documentation, which will look something like this:
https://<username>:<pass>#domains.google.com/nic/update?hostname=<domain>&myip=<ipaddr>
Note that the URL might be different depending on your FRITZ!Box type.
For further information check out the Google Domains help page Learn about Dynamic DNS
(especially the section "Use the API to update your Dynamic DNS record") and the help page of your FRITZ!Box, which may be accessed using the question mark icon in the top right of the DynDNS configuration page. (Help page for FRITZ!Box 7590)
You need to change the URL into following syntax
https://username:password#domains.google.com/nic/update?hostname=subdomain.yourdomain.com
Use the userdefined DynDNS provider.
Update-URL: https://domains.google.com/nic/update?hostname=mydyndns.yourdomain.com
Domainname: mydyndns.yourdomain.com
Username: generated username from Google Domains
Password: generated password from Google Domains
Related
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 2 years ago.
Improve this question
I've tried all of the steps in the instructions, but always get an error at #5 when it is supposed to redirect to google.com.
https://developers.google.com/nest/device-access/authorize#link_your_account
The error:
Authorization Error
Error 400: redirect_uri_mismatch
The redirect URI in the request, https://www.google.com, does not match the ones authorized for the OAuth client. To update the authorized redirect URIs, visit: https://console.developers.google.com/apis/credentials/oauthclient/${your_client_id}?project=${your_project_number}
I've ensured I have the right numbers- without spaces in the url and have put it in notepad and deleted all of the returns so it is one line of text.
any ideas?
What do you have listed in the Authorized Redirect URIs for your OAuth client in GCP, and what is the exact PCM URL you used? You shouldn't get this error if the redirect_uri and client_id parameters in the PCM URL matches what you have in GCP for the client.
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 9 years ago.
Improve this question
I have a link structure that is managed by an apache server. Some pages can be called with different url but with a php redirect the user will see just the canonical url for the page.
canonical url: www.example.it/490/persons/jan-antone-vian
generic url that call the same page: www.example.it/490/
My question is if it is correct to insert the url with just the id (www.example.it/490/) in some links (is much easier to manage the links) for SEO?
first of all, it's sure that a well constructed URL is better for SEO (url with keywords)
What you can do, and what you seems to have done :
keep the www.example.it/490/ URL for sharing,
add a 301 redirection to your
www.example.it/490/persons/jan-antone-vian when arriving in the first
url (www.example.it/490/). The SEO juice should be transfered to the
full url constructed.
Google says that ONE (and only one) URL has to be related to ONE (and only one) content, so you cannot let the both url displaying the same content. (you could be penalised for duplicate content...)
Note that a 301 is announced that it transfers the FULL SEO JUICE, but it's common to not do many 301 redirections in cascade.
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 9 years ago.
Improve this question
I have a server and every page has a redirect to use the SSL (https) using htacess. My question is what if someone types in the url http://www.domain.com/ and it redirects to https://www.domain.com was the information sent in the original request un-encrypted?
was the information sent in the original request un-encrypted?
Yes, the http://domain.com/ request is unencrypted, as is the response that contains the redirect. The SSL handshake happens before any data is sent, and until the browser knows to initiate an SSL handshake on the SSL port, everything is unencrypted.
Jon Lin's answer is correct. If this is a security concern, then it's best to ensure that the user only connects to your site by way of https, or redirecting from their first connection, before any sensitive information is sent. This can be done using the .htaccess file.
Yes the information passed via http protocol remains unencrypted. All the communication via http will be then unencrypted. Redirection occours after transmission of packet to the redirecting server so this communication can not be encrypted just by redirecting to https site.
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.